Storing an object in Session, is that a good practice
843844Feb 11 2010 — edited Feb 16 2010Hi,
In application, I have a class that is very much important class, that is very much important for every backing bean class. So I am initializing at the time of login and keeping that object in the session and every time when ever the application requires it takes from the session and uses, So now my doubt is, is that a correct procedure to keep that such a valueble object in the session, in the security point of view will it makes any problem?
actually previously I have written like, every backing bean extends this important class so after that I thought for very time it initiates the parent object for every view so I thought to reduce the heap size at runtime I kept this object in the session and when ever the application gets the requirement it gets from the session and it uses with the object
Please any one give the valid suggestion...