--- On Tue, 9/9/08, Martin Cooper wrote: > This smells like reinventing a subset of Commons Validator > just for S2. Can you convince me otherwise?
My initial motivation was to create a stop-gap, extensible mechanism for adding custom JavaScript validators without having to do a major XW/S2 revamp. The current mechanism doesn't really provide any support for that; my solution was 10-20 lines of JavaScript. There was discussion some time back about re-vamping XWork's validation; I don't know what the end result of that conversation was. If there's a reasonable way to specify JavaScript validation methods in the XWork config I'd prefer that. For example, if we could pass a param to the field validators, whatever, that's fine. If the answer is to create a commons-validator mechanism for S2, that's fine too (as long as I don't have to put my JavaScript in an XML file), although I don't know what the cost of adding OGNL support to the messages would be. I'd guess they could be evaluated against the stack. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
