Thanks David. This was the only workaround I could think of as well.
Yet it doesn't make sense to me - why are all the non-Collection fields
on the form maintained (i.e. upon returning the input page text fields,
etc. are all populated with previous values), but the Collections are not?
Anyone
--- Joe @ Team345 [EMAIL PROTECTED] wrote:
Thanks David. This was the only workaround I could think of as well.
Yet it doesn't make sense to me - why are all the non-Collection fields
on the form maintained (i.e. upon returning the input page text fields,
etc. are all populated with
when your web application starts up and
then a
single copy is available to all users.
robert
-Original Message-
From: Joe @ Team345 [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 13, 2003 9:26 AM
To: Struts Users Mailing List
Subject: Re: Validator, DynaForms, and Collections
That's it - I was looking at it from the wrong perspective and could
make sense of it.
Thanks!
Joe
David Graham wrote:
--- Joe @ Team345 [EMAIL PROTECTED] wrote:
Thanks David. This was the only workaround I could think of as well.
Yet it doesn't make sense to me - why are all the
Hi,
I'm using the Struts Validator (version 1.1 release) on DynaValidatorForms.
Everything seems to work just fine on forms that don't have collections on
them. However, several of my forms have pull-down lists where I do
something like:
bean:define id=reasons name=MyFormName
Make sure your collection is stored in the session. If it's in the
request you will lose it when returning to the input page.
David
--- Joe at Team345 [EMAIL PROTECTED] wrote:
Hi,
I'm using the Struts Validator (version 1.1 release) on
DynaValidatorForms.
Everything seems to work just
is the action that precedes the JSP.
Denis
- Original Message -
From: Joe at Team345 [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, September 12, 2003 11:30 AM
Subject: Validator, DynaForms, and Collections
Hi,
I'm using the Struts Validator (version 1.1 release
7 matches
Mail list logo