Hi, As Rahul explained, it would be better to use setAttribute() of Request Object instead of using session to store the data. Again if you need those stored data for long time use session object. If you need those stored data only for that request, then use Request object.
Bye mohan -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of Rahul Sent: Saturday, January 11, 2003 8:01 AM To: [EMAIL PROTECTED] Subject: Re: Keeping all the records to be displayed in session Importance: High hi, In my opinion option 1 is good enough. You could however go ahead with option 2 if you make small change in the architecture you have mentioned: Instead of storing the data in HttpSession you could store it in java beans/data transfer objects and pass the information to the jsp/view by using the setAttribute method of the request object. This should ideally be done in your dispatcher(it could be the front controller in your case). For the above to happen you must use forward method of the RequestDispatcher. Still, option 1 is always the easier one if you are not going to have multiple views displaying the same information, in which case the option 2 should be followed in order to have separation/independence of the presentation and the business layers. Regards Rahul ----- Original Message ----- From: "Ashwani Kalra" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 08, 2003 7:27 PM Subject: Keeping all the records to be displayed in session > hi, > > On one of the architecture decision there are two options in our current > project : > > 1. Front Controller--> jsp-->java bean/business delegate--> service > locator-->session--bean-->dao-->DB--> Displays the records > > 2. Front Controller-->event hander--> service > locator-->session--bean-->dao-->DB--> put all records in > HttpSession-->jsp-->retrieves record from session and displays the records. > > I suggested option 1 . because in 2nd option there are large no of records > put in session which will strain the web server and its not scalable. What > is your opinion ? > > > Regds > Ashwani Kalra > > ======================================================================== === 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".
