Hi Ana,
> Does
> it point to the fact that their requirements were pretty simple or they did
> some designs like maintaining sessions in the web server and not in the ejb
> server??
**********
I am wondering how do you manage this. If the bean is contacted through the
servlet, the session maintainance needs to be carried out by Servlet only.
Correct me If I am wrong.
***********
>
> I really dont get what value add I am getting from using EJBs if I dont go
> for entit beans or stateful session beans. AFAIK it is not a good design to
> make the clients session aware --- and thats precisely why stateful session
> beans came into being.
******************
Is it the reason??
******************
> But then people say it is too slow and go back to
> 1> Either storing the session info in HttpSession in the servlets engine OR
> 2> Storing session info in a hastable like data structure in the ejb server
> side -- something like a dependent object to the ejbeans.
> ie back to square one!
*************
It really baffles me how does the stateful session bean can make a client code,
not take care the responsiblity of the session tracking??. I am talking about
the scenario using the servlets, which is quite popular.
*********
--Sripada
===========================================================================
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".
