<Kevin>
Ideally you want to use single-instance session beans and store the
session information in the HttpSession (if this is correct or not, please
elaborate).
</Kevin>
There are "religious" discussions going for a while rregarding whether to
keep client state information in HttpSession and avoid stateful beans
altogether or to keep it in stateful bean.
The positions of the sides are depending on how well their container
supports stateful beans. Since WebLogic is by far the most used EJB
container and it does not seem to be able to handle well stateful session
bean this is where this conception of keeping state in HttpSession is coming
from. However there are other containers that provide decent performance on
stateful session bean.
If that is the case, keeping state in session bean is preferrable due to
potential support in future EJB containers of stateful bean failover.
And if you do not need failover - why would you go to the trouble of using
EJB at all given its current immature state and problems.
JSP/ActionServlet/business logic classes/JDBC should handle the job just
fine, unless your logic needs heavy transactional capability and failover.
Vadim Shun
NEW Corp
Dulles, VA
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
