I agree commons-validator shouldn't have code that mentions Servlets or Struts, but they would benefit from a validator that uses jexl, which I believe isn't tied to servlets (I could be wrong here). If I'm not, why not put the el validator in commons-validator, but add a hook for folks like Struts to add variables in the immediate scope, ala Velocity and Velocity tools.
Don Joe Germuska wrote: > At 5:12 PM -0700 5/10/05, Don Brown wrote: > >> 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
