If you are looking into a clustered environment, then you need to
go for stateful session beans to manage the value objects (ofcourse the
value objects should be serializable for most of the app server implementations)
If you have value object pattern being supported in the business tier
as well, then it will be easy to manage them from a stateful session
beans rathar than httpsession objects. There are tools avaialble to
support the value object pattern automatically in the business tier.
Dominic
On Wed, 5 Sep 2001 11:23:25 -0400, Scott Stirling <[EMAIL PROTECTED]> wrote:
>One of the recommendations is to use HttpSessions unless you need to support
>non-Web clients.
>
>
>Scott Stirling
>JRun QA
>Macromedia
>
>-----Original Message-----
>From: Dawn Lewis [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, September 05, 2001 11:13 AM
>To: [EMAIL PROTECTED]
>Subject: [EJB-INT] Maintaining State - Design Question
>
>
>Hi,
>I'm curious how everyone else has designed their system to maintain state.
>Are most of you maintaining state on the presentation tier until the user is
>ready to submit and save their changes? Are you putting your ValueObjects
>in the HTTPSession?
>
>Or, are any of you using Stateful Session Beans to maintain your state on
>the Business Tier. Passing ValueObjects as the user goes from page to page.
>Then, when the user is ready for the final save, inform the Business
>Delegate to persist the data.
>
>Is there a recommendation in the J2EE Patterns on which direction to go?
>I've read all of them, but for some reason, can't think of this being
>discussed.
>
>Thanks for any feedback!
>Dawn
>
>Dawn L. Lewis
>Southwest Airlines
>Fuel Managment, Systems Department
>(214) 792-3966
>[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
>
===========================================================================
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".
