Might even be better to put in an XML version check (either using the DOCTYPE or a specific <version> tag or attribute) to make sure that the correct version is being used. (*Chris*)
On 11/24/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
On 11/24/06, Paul Benedict <[EMAIL PROTECTED]> wrote: > Niall, > > This sounds like an enhancement request. If the validator methods do not > match, perhaps that advice should be in the error message that Struts > generates? Maybe a message like "method(x,y,z) requested but signature > is method(x,y,z,a): correct validator-rules.xml" ? Yes good idea - comes up often enough - change the exception message in Commons Validator, wouldn't be able to refer to validator-rules.xml though as thats a Struts artifact. If you want to open ticket for it: http://jakarta.apache.org/commons/validator/issue-tracking.html Niall > Niall Pemberton wrote: > > Paul meant replace the "validator-rules.xml" thats shipped with > > Struts. Sounds like you have an old version. The signatures hes > > referring to are the "methodParams" element in the validator > > definitions. You get this error when whats specified there doesn't > > match up with the actual method signature in the java class > > (FieldChecks for standard struts validators) > > Paul > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
