WAS 6.1 and Session Persistance

For the passed few weeks, I have been trying to come up with a way to persist some data across web applications deployed under WAS 5.1. We have discussed many options, but had narrowed the choices down to two. Since those were chosen, I have been implementing one of them, despite it being something we may not want to do ultimately. It would work, but it does not really attack the problem at hand.

Friday it came to my attention that in WAS 6.1, if you deploy web apps under a single EAR, a simple change in the deployment descriptor of the applications will allow the session information to persist across the applications in each ear.

This is a good thing, but would require some rethinking about the organization structure of our applications. Despite that, it would solve a good chunk of the problems we have been trying to figure away around. The bad news is that it completely voids what I have been developing for the passed few weeks. Ill trade it if it works...

This comes at a good time as well because we are preparing to migrate to WAS 6.1 anyway. Soon, I will be testing this, and will put more information up here when it becomes available.