Kevin,
you can pull up archives of EJB-Interest list, there have been some
discussions there for a while.
The bottom point is you probably need to test it with your EJB container.
Some reported trying to use Stateful session beans with horrible performance
results with their container, which led to a recommendation of storing
session specific info in servlet HTTPSession instead and abandoning stateful
bean altogether(if I am not mistaken, WebLogic is one of such containers),
with the client passing session context to stateless bean each time. Some
containers manage stateful session beans without significant performance
degradation, in that case you can use stateful session beans.
So the best way is to search EJB-Archives and see if your container is one
of the worst performing with stateful beans, or test your container, or just
ask on EJB-Interest this question.
Vadim Shun
NEW Corp
Dulles, VA
-----Original Message-----
From: Kevin Duffey [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 03, 2000 7:18 PM
Subject: Re: More on Model 2 discussion - Interesting option to Action
Class approach.
...
Another question which I believe pertains to this. Craig, you already said
to use stateless ejb. So..if I have a multi-page form, in some cases the
next form is built based on the previous forms data, do I store the data
from all these forms on the web-server servlet-container HttpSession? Or is
there some other mechanism for keeping state for a particular client on a
multi-page form?
...
===========================================================================
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
