Has anyone ever nested form beans with collections more than one level
deep?
We have a situation where we have a form bean that contains another form
as an attribute, which in turn contains a list of other smaller forms.
The page renders fine, but when the form is posted the updated values in
the
> -Original Message-
> From: Erik Weber [mailto:[EMAIL PROTECTED]
> Sent: February 14, 2005 8:39 AM
> To: Struts Users Mailing List
> Subject: Re: Validation Strategies?
>
>
> What I'm suggesting would not cause duplicate validation logic. The
> (business) validation logic is still perf
> -Original Message-
> From: Erik Weber [mailto:[EMAIL PROTECTED]
> Sent: February 14, 2005 8:19 AM
> To: Struts Users Mailing List
> Subject: Re: Validation Strategies?
>
>
> I use Struts' declarative exception handling abilities to handle
> manager-layer validation errors. Exceptions
> -Original Message-
> From: Martin Gainty [mailto:[EMAIL PROTECTED]
> Sent: February 14, 2005 8:20 AM
> To: user@struts.apache.org
> Subject: RE: Validation Strategies?
>
>
> Being a former DBA
> I would wonder if this design would adhere to
> First Normal
> Second Normal
> Third Normal
> -Original Message-
> From: Vic [mailto:[EMAIL PROTECTED]
> Sent: February 14, 2005 8:01 AM
> To: user@struts.apache.org
> Subject: Re: Validation Strategies?
>
>
> That is the struts way (and it makes it "secure")
> .V
Vic,
OK, what form do these maps take - XML, properties files, et
Hi folks!
My apologies if this has been asked before - I looked through the FAQ's
and archives, but couldn't find any pertinent answers.
We have several applications that use a common code base, and have both
a Swing and Web (Struts/JSP) front end. The business validation logic
for the applicati
6 matches
Mail list logo
