Hi kumar,
But when a stateful
session bean instance is persisted, if any of its non transient
fields contain a reference to the SessionContext, that has
to written to persistent storage. Thats what the spec says.
So why is SessionContext not made
serializable itself?
If it *only* to give the container
vendor freedom to choose his custom object persistence mechanism?
----- Original Message -----
Sent: Wednesday, October 19, 2005 10:04
PM
Subject: Re:
javax.ejb.SessionContext
-->
Hi
Session
context is not serialized as it represents the session environment and
normally it does not change and available as long as application is running.
So thatÂ’s why generally context objects are not
serialized.
From:
A mailing list for Java(tm) 2 Platform, Enterprise Edition
[mailto:J2EE-INTEREST@JAVA.SUN.COM] On Behalf Of Bharath
Ganesh
Sent:
Wednesday, October 19, 2005 7:51 PM
To:
J2EE-INTEREST@JAVA.SUN.COM
Subject:
javax.ejb.SessionContext
Could anyone tell
me why is javax.ejb.SessionContext not made serializable?
===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body of
the message "signoff J2EE-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body of
the message "signoff J2EE-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body
of the message "signoff J2EE-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".
