Sorry I'm not really sure what you mean by "chrome bean". Or how one would go about scoping one to session while the action form (dyna or otherwise) is scoped the request.
Do you mean you have a bean that persists beyond the form submission in which you can store the user input until such a time that it can be passed up to the model? (thus placing the action form back into the presentation layer)
Many thanks
Mark
On 11 Dec 2003, at 12:03, Ted Husted wrote:
I've lost track of the underlying use case for this thread, but if it's about populating input options on a form, you might consider using a second object for storing these types of options. For a time, some of us were starting to use the ActionForm to represent the input options along with the input values. This notion had more to do with code maintenance than architecture. At this point, I would suggest using finely-grained DynaActionForms to represent only the input required by an action. All other constructs, like arraylists for select boxes and so forth, can be put on a second "chrome" bean. A distinct advantage here is that you can scope the chrome bean as appropriate. A global default can live in applidcation scope, and other can live in session or request scope, as appropriate to a request.
HTH, Ted.
Andy Schmidgall wrote:Does this mean it's impossible to do through request scope? I am
attempting to do this, and it would be nice to know if my work is in
vain :)
-Andy
-----Original Message-----
From: Yee, Richard K,,DMDCWEST [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 3:20 PM
To: 'Struts Users Mailing List'
Subject: RE: dynamically sized form (mostly solved)
I thought it worked, but it didn't.
-Richard
-----Original Message-----
From: Nifty Music [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 1:02 PM
To: [EMAIL PROTECTED]
Subject: RE: dynamically sized form (mostly solved)
Nicholas, What you said definitely makes sense to me. Richard graciously replied
off-list with a similar response. I remember reading documentation
which stated that when using dynamic arrays with DynaForms, it is
necessary to place the DynaForm in session scope. However, I 'm almost
positive that someone (Matt? Mark?) mentioned on this list that they
were able to pass an ArrayList through a DynaForm in request scope. For
a variety of reasons, I'm not too eager to put the entire formbean in
the session for the sake of propogating one ArrayList attribute. If
Matt or Mark or anyone else has some insights to share regarding how
they were able to get this to work in request scope, I'd be very
grateful to hear. Thanks again,
Brent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
