Evan Ireland wrote:
> Rickard �berg wrote:
> >
> > Hey
> >
> > Richard Perks wrote:
> > > I am trying to run a simple statefull session bean within WebLogic 4.5.1 but I
> > > get exceptions rased during the activation / passivation process. Is this a
> > > WebLogic internal error as I can't see what is wrong with by EJB ?
> >
> > SessionContext's aren't serializable. In EJB1.0 you should define the
> > variable as transient. With EJB1.1 the container must be able to take
> > care of this issue for you.
> >
> > I.e. set it to transient, but remove the transient thing as you move to
> > EJB1.1.
>
> If you make the SessionContext instance variable transient, there is no way to
> restore it in ejbActivate, and the server will not call setSessionContext
> again. For EJB 1.0, although there is no specific mention of it in the spec,
> I can't see that there is any way to support passivation/activation without
> making SessionContext serializable, or otherwise having the container able to
> restore it using reflection.
>
> I believe that this reported problem indicates a bug in the EJB server.
>
> ===========================================================================
> 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".
According to weblogic engineers, they guarantee that the container maintains the
context eventhough you must declare the context transient. Magic happens! Have been
using weblogic for over a year -- it works fine.
===========================================================================
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".
