Re: request attributes and failed validation

[Michael McGrady]

I assume you want to do this after the validation fails, i.e. that timing 
(when) not placement (where) is the issue.  Exactly how you want to do this 
depends on the details of your application.  Not knowing these details 
makes it difficult, but just guessing would lead me to think that having 
something like a Composite Pattern in the session would make sense, to 
borrow some good ideas from the J2EE boys.  There are just so many ways you 
could do this.  The tracking and performance of the "cursor," as it were, 
is completely up to you.  That is one of the nice things about Struts: with 
few exceptions, you have enough control at every stage to do whatever you 
want to do.  You can, for example, make validation "fail" in numerous 
ways.  You are not stuck with any particular paradigm.  You can do it the 
usual way usually, but in your case, maybe you need to have it "fail" with 
a little more controller designed activity.  Does this make sense to you 
when put this way?

Michael McGrady



At 12:01 AM 1/31/2004, you wrote:
It's not slow, the lists are created from data from a database.  I am 
assuming when you say 'do it again' you mean add these Lists to the 
request.  Where should this be done at?

>>> [EMAIL PROTECTED] 01/31/04 01:48 AM >>>
One way is to put them temporarily in the session.  But, why not just do it
again?  Is it too slow?
At 11:28 PM 1/30/2004, you wrote:
>In my Action I am populating an ActionForm with data from a database.  I
>am also setting some additional request attributes with Lists of
>beans.  The purpose of these Lists are to create various drop down boxes
>in the form.  This works well, however when the form is submitted and
>validation fails these attributes are no longer in the request and the
>drop down boxes aren't created.
>
>What is the best way to have these Lists avaiable when the validation fails?
---------------------------------------------------------------------
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]