Hello everyone,
I was wondering what the best solution would be to hold Session information in a J2EE application.
If I develop an application using JSP, Servlet and EJB technology where should I hold all the session information.
In a previous project we chose to hold everyting on the EJB side. Keep the HttpSession as empty as possible. We had one Stateful session bean that holds all session info.
We did this because some Java Architect told me that an EJB container can be scaled better opposed to the Web-container.
But I read somewhere that Stateful session beans don't scale so well.
So what is the best decision? Keep everything in the HttpSession or keep everything in a Stateful session bean? Or is there an even better solution.
What is best for a really big application?
Greetings Manuel
I was wondering what the best solution would be to hold Session information in a J2EE application.
If I develop an application using JSP, Servlet and EJB technology where should I hold all the session information.
In a previous project we chose to hold everyting on the EJB side. Keep the HttpSession as empty as possible. We had one Stateful session bean that holds all session info.
We did this because some Java Architect told me that an EJB container can be scaled better opposed to the Web-container.
But I read somewhere that Stateful session beans don't scale so well.
So what is the best decision? Keep everything in the HttpSession or keep everything in a Stateful session bean? Or is there an even better solution.
What is best for a really big application?
Greetings Manuel