Re: Stateful Session Beans

[GlennODickson]

This is interesting! May then please ask :   1. Where  would be an appropriate in this structure to place a bean that holds the customers login details and session state ? Would you create another bean called CustomerSession (SFSB) or make the Customer Service a SFSB? >>>>>>>>>>> I think it is better you can have Customer Service as SFSB.   why? How does one know when to make something like, CustomerService a SFSB or SLSB? I gather by making it SFSB the client would still create the SFSB and insert it into the Session right?       2. How would this SFSB be referenced ? I don't understand how the SFSB can be retrieve at some time later to use the session details. >>>>>>>>>>> Use Handles and store these Handles in the HttpSession. These will be referenced just like how you are referencing SLSB from your client. For display alone you can use SLSB or direct call to DB. For other things like insert , update and delete you can use SFSB with EB.   It is not always needed to have SLSB in your tier. It depends on your requirements. A direct access to the DB thru JDBC2.0 can be much faster than  thru EJB’s. Make use of your design patterns for EJB. They will help you a lot. They actually gives you to sae much of your coding breaking with Transaction related things   When it is not necessary to have SLSB in the tier? Direct access thought JDBC would imply a 2 tier model am I correct in assuming you are implying this? Why use SLSB for direct DB calls for display and other things SFSB with EB? Why not have all calls going through SLSB and state data and related state methods in SFSB?         ----- Original Message ----- From: Kesavanarayanan, Ramesh (Cognizant) To: 'GlennODickson' Sent: Thursday, September 12, 2002 12:37 PM Subject: RE: Stateful Session Beans   Hey thanks for your comments I would like to ask then:   I do have this structure :   action class(struts) <---->webTier Controller (class) <-------> EJB Business Delegate(SLSB) <--------> Customer Service (SLSB) <------> Customer (Entity Bean)     1. Where  would be an appropriate in this structure to place a bean that holds the customers login details and session state ? Would you create another bean called CustomerSession (SFSB) or make the Customer Service a SFSB? >>>>>>>>>>> I think it is better you can have Customer Service as SFSB.   2. How would this SFSB be referenced ? I don't understand how the SFSB can be retrieve at some time later to use the session details. >>>>>>>>>>> Use Handles and store these Handles in the HttpSession. These will be referenced just like how you are referencing SLSB from your client. For display alone you can use SLSB or direct call to DB. For other things like insert , update and delete you can use SFSB with EB.   It is not always needed to have SLSB in your tier. It depends on your requirements. A direct access to the DB thru JDBC2.0 can be much faster than  thru EJB’s. Make use of your design patterns for EJB. They will help you a lot. They actually gives you to sae much of your coding breaking with Transaction related things.   HTH.   ? Ramesh Kesavanarayanan  ?    [EMAIL PROTECTED]