Doh. I was being very stupid - I looked in the XWork source and
realised it's really straightforward.
I'm blaming this one of lack of sleep :)
Cheers,
Andy.
On 25 Jan 2009, at 01:25, Wes Wannemacher wrote:
On Saturday 24 January 2009 20:17:49 Andy Sykes wrote:
Actually, having an intercept
On Saturday 24 January 2009 20:17:49 Andy Sykes wrote:
> Actually, having an interceptor makes some sense in this case.
>
> How can interceptors "short circuit" the stack and action to return a
> result code? The ideal situation here would be that the "protector"
> interceptor is above the validati
Actually, having an interceptor makes some sense in this case.
How can interceptors "short circuit" the stack and action to return a
result code? The ideal situation here would be that the "protector"
interceptor is above the validation interceptor, checks for the form
token, and chucks an
Andy Sykes wrote:
Cheers for the suggestions - I guess I was just looking for a sanity
check from the list.
It seems reasonable to me--the functionality *could* be wrapped up in an
interceptor, which might be marginally cleaner, but it's one of those
judgment calls that in real life I probabl
Hi all,
Cheers for the suggestions - I guess I was just looking for a sanity
check from the list.
My current method (almost exactly the same as below) is to check a
choice form field for null in the validateXXX() method - this is the
case when you call the action without POST from a form.
Andy Sykes wrote:
My forms all submit to a different action than that which renders the
pages.
Is there a recommended way to prevent/mitigate the effect of users
directly calling the actions (via their URL) that forms are submitted
to? In this case, the actions' fields are null, which is some
ed
> recipient. Sender does not necessarily endorse content contained within
> this transmission.
>
> > From: a.sy...@ucl.ac.uk
> > To: user@struts.apache.org
> > Subject: Only call actions from certain forms
> > Date: Fri, 23 Jan 2009 23:19:34 +
> >
&
this transmission.
> From: a.sy...@ucl.ac.uk
> To: user@struts.apache.org
> Subject: Only call actions from certain forms
> Date: Fri, 23 Jan 2009 23:19:34 +
>
> Hi all,
>
> My forms all submit to a different action than that which renders the
> pages.
>
Hi all,
My forms all submit to a different action than that which renders the
pages.
Is there a recommended way to prevent/mitigate the effect of users
directly calling the actions (via their URL) that forms are submitted
to? In this case, the actions' fields are null, which is somewhat
9 matches
Mail list logo
