Allistair Crossley wrote the following on 9/20/2004 6:12 AM:
DynaValidatorForm dynForm = (DynaValidatorForm) form;
ActionErrors dynFormErrors = dynForm.validate(mapping, request);
I just tested this and it works fine.
--
Rick
-
To
ill
tie up with the declarative validator-rules.xml/validate.xml files?
ADC
> -Original Message-
> From: Rick Reumann [mailto:[EMAIL PROTECTED]
> Sent: 18 September 2004 20:00
> To: Allistair Crossley
> Subject: Re: DynaActionForm and previous request attributes (no answer
>
Allistair Crossley wrote the following on 9/17/2004 8:40 AM:
however, because I am forced to use a tile definition or JSP in the
input parameter of the action for when the validation fails, i am unable
to load page attributes for that pid from my backend navigation system
and this is breaking my vi
not quite .. when i arrive initially at the view governed by somePage.jsp yes, there
are a bunch of request attributes set up. on this page is my form. as a hidden
variable to the form I copy the existing page id because this must be present for our
SecuredBaseAction to know what properties to l
nal Message-
> From: Adrian Kaminski [mailto:[EMAIL PROTECTED]
> Sent: 17 September 2004 13:33
> To: Struts Users Mailing List
> Subject: Re: DynaActionForm and previous request attributes (no answer
> found in archives for similar problems)
>
>
> > managing a reque
AIM: jmitchtx
> >
> >
> >
> > - Original Message -
> > From: "Allistair Crossley" <[EMAIL PROTECTED]>
> > To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> > Sent: Friday, September 17, 2004 7:58 AM
> > Subject:
> managing a request attribute in the session by setting it and then making sure we
> pop it out at the view is messing and defies the semantic use of the request scope.
>
> that's why it is bad practice.
>
Don't shoot me if I'm wrong but HTTP is stateless so without any of:
cookie, session, bro
K Chukkavenkata [mailto:[EMAIL PROTECTED]
> > Sent: 17 September 2004 12:51
> > To: Struts Users Mailing List
> > Subject: Re: DynaActionForm and previous request attributes (no answer
> > found in archives for similar problems)
> >
> >
> > I would agree with hi
; -Original Message-
> From: James Mitchell [mailto:[EMAIL PROTECTED]
> Sent: 17 September 2004 13:02
> To: Struts Users Mailing List
> Subject: Re: DynaActionForm and previous request attributes (no answer
> found in archives for similar problems)
>
>
> What is 'bad
>
Sent: Friday, September 17, 2004 7:58 AM
Subject: RE: DynaActionForm and previous request attributes (no answer found
in archives for similar problems)
but that's bad practice. very bad.
> -Original Message-
> From: Jitender K Chukkavenkata [mailto:[EMAIL PROTECTED]
>
but that's bad practice. very bad.
> -Original Message-
> From: Jitender K Chukkavenkata [mailto:[EMAIL PROTECTED]
> Sent: 17 September 2004 12:51
> To: Struts Users Mailing List
> Subject: Re: DynaActionForm and previous request attributes (no answer
> found
I would agree with him. I can suggest you the same.
Jitender Kumar C.V.
> Now, my understanding was that DynaActionForm manages to populate a map of
> form fields, match them up against validation rules, and if it fails, it
> would KEEP the previous request but add errors into it and FORWARD back to
> the view, therefore KEEPING all the request attributes. It does not
13 matches
Mail list logo
