>From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> > >How would you suggest we deal with those blasted checkboxes using this
> > approach? If the
> > >checkbox is unchecked, the browser doesn't send the field name at all
>-- so
> > there is no
> > >way for Struts to know that this field is on this page.
Agh! I never new that!
>"Jones, Dean" wrote:
> > And approach I was looking at in a previous toolkit was that, if you
>are
> > using your
> > own tags to put the fields there in the first place ( which you usually
>are in
> >
> > Struts ), then you know they are there, and what their type is ???
Thats it - the perfect solution. Do it during the page build. I take it the
custom tags have access to the form beans?
>That makes sense ... but now aren't you still back in the boat of having to
>modify the form bean when your page designers reorganize which fields are
>on
>which pages again?
Not if the field-to-page map is being generated dynamically during the page
generation.
With this type of implementation you can treat your form bean like a single
page form and just let the presentation layer deal with displaying the
errors and moving the pages.
Ned.
_____________________________________________________________________________________
Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
