I had a similar problem in my application. I had to maintain the session for a user
all the time he is logged in.( i am talking about users logged for a e-school
application) So instead of using a StateFullSessionBean what I did was to store the
required state in a simple object(also known as Replicated Object ..refer to
http://jerry.cs.uiuc.edu/plop/plop99/proceedings/brown/brownfinal.pdf) that are passed
from one request to the next through a session object in a JSP or a Servlet.
I will try to relate this to the (in)famous shopping cart example
Let say the user shops in one session and adds his items to the cart.
so for our purpose we can make a SelectedItemsBean(this a serialized object). This
object tells us how is shopping(userID) and what he added to the cart(can be any type
of collection object but it must be serializable).
So I make the scope of this SelectedItemsBean to be session and pass it from one
request to the next untill he finishes his shopping. At the end I will pass this
SelectedItemsBean to the StateLessSessionBean that will do the rest of the work.
This worked for me and I could see a performance increase over using a SFSB.
Cheers
sesh
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
