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
gt; James Mitchell
> Software Engineer / Open Source Evangelist
> EdgeTech, Inc.
> 678.910.8017
> AIM: jmitchtx
>
> ----- Original Message -
> From: "Allistair Crossley" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, September 17,
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
ber 17, 2004 8:09 AM
Subject: Re: DynaActionForm and previous request attributes (no answer found
in archives for similar problems)
> how to invalidate the session when user clicks the close(cross) button
> which will display at the right side of the browser when we open a
> page..
>
>
> 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.
chtx
- Original Message -
From: "Allistair Crossley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 17, 2004 7:00 AM
Subject: DynaActionForm and previous request attributes (no answer found in
archives for similar problems)
Hi All,
I am c
Hi All,
I am coming up against a limitation of using DynaActionForm that I wonder if someone
can confirm or deny.
All our Action classes extend a SecuredBaseAction. This SecuredBaseAction does a few
important things per request like making sure the user is validated and also loading
page prop
14 matches
Mail list logo