I have a client servlet that will need to look up a particular instance of a
stateful session bean....
I know it sounds wrong, but hear me out.
The stateful session bean represents a person who has logged into the
portal.
I don't want to tie the client to that one session bean instance. If the
servlet engine that holds the reference to the session bean crashes, the
user (that the session bean represents) would have to re-login.
What I want to do is for each stateful session bean, store its EJBObject in
LDAP (bound by sessionid value). Then as each client needs to access the
stateful session bean, it could look in JNDI with the sessionid and get the
EJBObject for the session bean and be able to address it.
On the other side of the equation is the case that the server that is
holding the session bean goes down. If I am using some sort of
container-specific feature that does stateful session bean failover, and my
client looks in JNDI to get a EJBObject for the stateful session bean, is
the reference still valid??
That is, if the stateful session bean has been replicated to another
instance of an application server, will the client be able to find this
session bean given that it is now in a different location. I know this may
be a container specific implementation issue, but would appreciate any
thoughts to this regard to how different app servers would handler this
scenario.
What are your thoughts on this? Shoot me down!!
Thanks in advance,
Phillip
Alcoa eCommerce
===========================================================================
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".
