I have a stateful session bean that represents a logged in user. The
client that creates the stateful session bean is a servlet. My worry is
that if the container that is holding this servlet goes down, I will lose
the session bean reference. The user would then have to re-authenticate.
In order for this to not happen, when the bean is created, I put the user
object into jndi, bound to the sessionid of the http session of the user. I
intend to make my jndi tree a netscape ldap server (replicated)
Now if the client would go down, a new client(a different servlet container)
would receive a request (with the session id), if it did not have a handle
to the user stateful bean (stored in HTTPSession), it could call the
UserHome object, with the session id. The user home object could then do a
JNDI lookup, get the user object and re-create the bean.
I am trying to break the tie between the
HTTP server, HTTP servlet container and the EJB container, so that if any
part goes down, the user's session bean is not lost and can be re-created or
retrieved with the session id token.
In addition to the case of an servlet container going down, this protects me
in the case that an application server goes down.
I would like to be shoot down!! I appreciate some constructive criticism!
Thanks,
Phillip
===========================================================================
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".
