Dwati xxx

According to the J2EE specification, every Context has his own session management.

The statement above may sound unspectacular first, but may turn out to be cumbersome.

All you need to do is click Add Mask for one or more columns and then Save to apply a mask for these fields.

I'll first describe how a sessionid can be passed from one Context to another Context (e.g. Next, I'll describe a basic technique to store objects into a central Context to be retrieved from other Context.

After reading this HOWTO, you should be able to share sessions across Contexts.

Note: This guide should apply to all J2EE containers.

Finally, I'll touch the area of making shared session data persistent to share it easily with other Contexts.

Dwati xxx-11Dwati xxx-63Dwati xxx-10Dwati xxx-25

Thus we knew right from the beginning that we will have session data to be shared across contexts.

However, how will Context B know that the same user has another session running at Context A?

If you plan to create bigger webapps, you'll surely notice that it makes sense to set up individual WAR files for individual applications.

This is when the J2EE spec comes into our way: Reading the session data of another Context has been deprecated for security reasons as of Java Servlet API 2.1.

Link: Javadoc reference So we'll have to find another way to share data between Contexts.

Leave a Reply