An EJBObject handle is serializable, so you can store it without worrying
when the webserver stores your http session persistently. However, storing
the remote stub is not advised as this generated class is not to be
guaranteed serializable across different vendor implementations.
As for storing a normal Java object in a session on the web server... this
sounds like a recommended approach since JSP's recent appearance. In this
approach, the bean corresponding to a page is stored in a session then
recreated, if persisted, to be filled with data from the JSP.
Jason
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Rakesh Rajendran
Sent: Wednesday, March 22, 2000 8:42 AM
To: [EMAIL PROTECTED]
Subject: Storing EJB in session object for tracking..
Hi,
Could somebody elaborate on the proper way of using a
StatefulSession Bean while passing it from one servlet to the other . Do i
add the Bean or the Bean's Handle to the Servlet session object and then
retrieve it later somewhere down the line to access some properties of the
bean . Which is the optimal way of doing it .? Please also tell me whether
substituting a normal java object with all the fields of the EJB instead of
a EJB will give major performance improvements .
It would be really great , if somebody could throw some light on the above
issues..
Thanks ,
R2
===========================================================================
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".
===========================================================================
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".
