Session: when you want to share your data in your whole application. like user_id. Request: its just use for forward and recieve the data between webpages but its data just shareable for next and last hit webpages.. not like session.
Originally posted by Rahul Bhattacharjee: You can try this , but would not recomend this.
Write a singleton repository , which can store key , value pairs and then place those classes in shared/classes , so that this is visible to all the web applcations.
what does that 'singleton repository' means?
It means, create an object with the singleton pattern and store it in shared/classes of the ear, so that both application can access it?
Jeroen T Wenting
Joined: Apr 21, 2006
simple: do NOT do this. If you need to send data from one web app to another store it in a database used by both or send http requests to servlets back and forth.
Do NOT attempt to write some class, instances of which you hope will be available to both applications. It's not going to work, and even if you think it does it's not at all scalable and extremely poor design.
Joined: Aug 15, 2004
You can choose, the most suitable one for you, from the list given by Ulf.