I after Wendy gave me the advice to rephrase the question I will try to
rephrase it.
Being new to struts, I want to know how people deal with data objects
which need a scope bigger than request but smaller than session.
I will give an example, you have some kind of wizard interface with
myriads of input fields distributed over multiple forms.
There are some ways to handle this
a) You can dump anything into the session, which means you run into
memory problems in the long run.
b) you can put everything into hidden fields, which means you have
myriads of hidden fields, which is slow and error prone to implement.
c) You can try to add the stuff manually to the session and remove it
later, which also is problematic in case of an error because then you
have a mem leak caused, by a tangeling object in the session.
Other frameworks have interesting approaches to solve this.
MyFaces has x:saveState which basically serializes the data objects away
and loads then once you reach the next page (and before the request
data is assigned)
Rails according to a friend has some kind of data structure which you
can tell to extend to the next request, where you can dump data.
And there is Shale with the dialog system, which allows you to specify
scopes smaller than session but bigger than request.
How is this problem resolved in struts in a proper manner?
Werner
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
