Both serve different purposes. I would use HttpSession objects to store
conversational state between browsers and the web application, and limit
stateful session beans for state of business transactions.
Pascuzzi Domenico wrote:
>
> Hi!
> I'd like to know if I can use Stateful Session Bean in order to track
> client session OR if I need HttpSession and Servlet classes.
> If so, how can I associate SUBSEQUENT request of a client to ITS CURRENT Session
> bean stateful?
> ..........With HttpSession and Servlet I used Session id and now?
> What about method getCallerIdentity? What is the format of this Identity?
> Is it static or changes through subsequent calls?
> Thank you very much!
>
> ===========================================================================
> 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".
