I have done much reading on multiple sites and found some dated info about my problem and I was wondering if there were better answers now that a few years have passed. I apologize if this question has been asked on this forum, but I did make an effort to find a similar
thread.
My situation:
Oracle 9i appserver and database
We currently run an aging application that is slowly being rewritten. One of the main problems of the old application is the entire business application is lumped into one application.
For example if we had a problem with one of areas such as accounting all of our divisions (HR, purchasing, etc) would have to be stopped because of accounting.
In future development they would like each 'department' if you will to have its own container, so in other words accounting one be container1, hr would be 2, etc.
The main problem I am coming across is certain employees will need to go back and forth between some of these applications because they work in multiple departments.
I usually store Employee ID information in the session when they login so they can be authorized as they move around, but the sessions do not share information if the container is switched.
For example:
Application 1 -- User signs in and authenticates, loads ID info, loads other info
User descides to use Application 2 linked from Application 1 (in a separate container) -- all ID info is gone, now it must be reloaded or reauthenticated.
In the forums the information I have read says that most app servers DO NOT support a way to share session information between containers, but I can't imagine our company is the first to try to implement something of this nature.
So how have people been getting around this problem?