Sortei:
Typically, you manage the 'connection' between your session bean instance
and
a specific client.
For instance, you can keep a reference to your session bean in as
a named value in your HttpSession. Use
HttpSession.putValue() and
HttpSession.getValue()
to access it.
-----Original Message-----
From: Soteri Panagou [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 09, 2000 12:36 AM
To: [EMAIL PROTECTED]
Subject: newbie question: http sessions --> servlets --> stateful
session beans
Hi
Sorry bout this newbie question, but am i missing something? can anyone
give me clarity on the following scenario:
1) I am using weblogic 4.5 application server;
2) i have a servlet acting as a front component;
3) I have a stateful session bean that handles user authentication and
Account detail retrieval
4) At the same level i have a stateless session bean doing credit card
authorisation
I have just built http session management into my servlet. my question
is this: If I have to use an HttpSession object to keep track of my user
connections, how does the stateful session bean handle this scenario?
i.e. How does the connection between a specific instance of the session
bean and a specific client get managed?
cheers
steri
===========================================================================
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".
