Would be based on the method name (does not consider the post/get), so with
DMI and a ?myMethod refresh, the validator validates without all the
necessary data (provided by ongl etc) and fails badly.  ie returns to INPUT
with all black fields.

I have tweaked my DMI interceptor to fail gracefully rather than blowing up!

if (dmiEnabled && "POST".equals(request.getMethod()) || !dmiEnabled) {
            doBeforeInvocation(invocation);
}

Cheers Greg

On 5 June 2018 at 12:33, Yasser Zamani <yasserzam...@apache.org> wrote:

>
>
> On 6/5/2018 3:25 PM, Greg Huber wrote:
> > Think is just a check on the logic.
> >
> > for a page refresh
> >
> > http://www/../edit/myEdit!save.action <http://www/edit/myEdit%
> 21save.action>
> >
> > will call the validator, whilst
> >
> > http://www/../edit/myEdit.action <http://www/edit/myEdit%21save.action>
> >
> > does not.
> >
> > If its not a post why validate the form?
>
> Well it seems Struts doesn't rely on HTTP METHOD to decide to do a
> validation or not because another user may correctly request this option
> on also GET or etc methods. Instead, Struts allows user to define two
> actions (they may even be on same class or even same method) but one
> having validation and another not having.
>
> Regards.
>

Reply via email to