Niall Pemberton wrote:
1) Do the "out of the box" falvours cater for your needs? There are 2
- using the form name as the validation key, or using the action
mapping.
Using the action mapping _might_ work, ... right now I'm doing this:
<action path="/entity"
type="mypkg.EntityAction"
name="entityForm"
scope="request"
validate="false"
parameter="action">
<forward name="create" path="page.admin.createEntity" />
<forward name="edit" path="page.admin.editEntity" />
</action>
But then I'd still need to call the validate() myself, and I'm not sure
how to specify mappings in the validations.xml file (if that's what you
were getting at).
2) If the 2 standard flavours don't suit your needs, then you could
create your own flavour by having a custom validator form
implementation and overriding the getValidationKey() method:
public FooValidatorForm extends ValidatorForm {
public String getValidationKey(ActionMapping mapping,
HttpServletRequest request) {
return ... // your own key
}
}
This might work... I'd just need to be careful not to use
static/instance variables.
- Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
