Comments on: Sharing session state between JEE web applications through WebLogic session descriptor of sharing-enabled Friends of Oracle and Java Wed, 15 Apr 2015 12:11:59 +0000 hourly 1 By: vijeta Fri, 25 Jul 2014 04:52:37 +0000 Hi Lucas

Thanks for this post , it is very useful.
we have enabled session sharing but we are not able to retrieve session managed bean used in one web module to other. will u please describe how u have used same session bean in 2 different pages of different modules.

By: Rick Tue, 03 Jun 2014 10:09:32 +0000 Hi Lucas

Thanks for this post , it is very usefull.

Can you please expand on the following statement
“Also note that much of each application’s definition can be deployed in a WebLogic Shared Library; these libraries (one per web application) can be deployed independently of the EAR file. So deployment does not have to be as massive as suggested above.”

How would this work given your example above?

Is there no getting around the requirement that one EAR must contain all web applications where session sharing is required?


By: sriramvelpula Thu, 10 Apr 2014 23:52:51 +0000 Hi Lucas,

Thanks for the detailed post. We are also running into a similar situation but in our case we want “Web1″ war file to be deployed in one cluster and “Web2″ war file to be deployed in another cluster. Will the same configuration work in our case??


By: Lucas Jellema Thu, 19 Jan 2012 07:55:01 +0000 Hi Michel,
Mike did indeed mention Coherence*Web. However, that requires a more than basic license model. In addition: is Coherence*Web meant just for session state sharing between cluster nodes (as well as fast serialization for single node systems) or is it also intended as a mechanism to share the session state between different web application – as I am looking for in this post?

Of course Coherence and any other Data Grid (or even any Static HashMap in the JVM for single node systems) can be used to store, retrieve and therefore share data – however, then the burden of managing some data in the session and other data on the grid is on the developer. With the approach described in this article, the session state is just shared without additional overhead.


By: Michel Schildmeijer Wed, 18 Jan 2012 11:21:57 +0000 Hi Lucas
Did Mike not talked about Coherence*Web? This gives you an even more reliable and robust session sharing.
You can use some coherence specific context parameter settings like enable session context, session length and caching possibilities.