Actually, the extras I was referring to was for the commons-validator project itself as I mistook the ticket for a validator ticket. The Beanshell and xpath validators required only the commons-validator project and had nothing to do with Struts. Ideally, all validators could be added to the commons-validator project and be immediately reusable in environments like Struts and Spring. Unfortunately, the code is currently too muddled for that so Struts has to create a wrapper for every new validator/validation.
Also, at least in this case, I think one of the strong benefits is the preparation of a meaningful expression evaluation context which includes references to the ActionForm and the request and session scope, etc. commons-validator has no business being bound to the servlet API or the Struts API. (I suppose you could treat the form as a POJO and cover one of those, but not both.)
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
