struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <>
Subject [jira] Updated: (STR-1142) ActionValidatorUtil
Date Tue, 13 Nov 2007 08:20:34 GMT


Paul Benedict updated STR-1142:

    Affects Version/s: Future
             Assignee:     (was: Struts Developers)

> ActionValidatorUtil
> -------------------
>                 Key: STR-1142
>                 URL:
>             Project: Struts 1
>          Issue Type: Improvement
>          Components: Extras
>    Affects Versions: Nightly Build, Future
>         Environment: Operating System: All
> Platform: All
>            Reporter: Brandon Goodin
>            Priority: Minor
>         Attachments: Action.txt,, ActionValidatorUtil.txt
> I just put together a class that uses the Validator from within a
> LookupDispatchAction. The class could be easily included into the Struts
> distribution. It is very useful to have the validation available to call
> from within the DispatchAction because different methods require different
> validation. Anyways, I have heard others speak of Action based validation
> (Craig included). This is not as useful in regular actions because the
> mapping allows for the flexibility. But for those of us who use the
> Dispatch... this type of validation is uesful. The code should be ready to
> drop in with no changes.
> FYI - The class extends DispatchAction and uses the same code as the
> LookupDispatchAction. I took the validation code from the
> ValidatorActionForm and included it in the ValidatorLookupDispatchAction
> class with some minor changes.
> I also, abstracted the method lookup process into a method 
> called "lookupMethod". This allows for the method name to be retrieved from 
> within the extended ValidatorLookupDispatchAction class for other purposes or 
> custom configurations that might be used.
> Basically, the key that is looked up in the validation.xml form name is the
> ActionMapping url plus a dot method name. (.i.e. / <- edit
> is the method name).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message