I've been thinking about the inclusion of the Struts driver/interface to the Validator with the Commons version. Some of my concerns are as follows. If Struts is included, what is the criteria for including another driver? I wouldn't want to be exclusive, but I wouldn't want to get into having to maintain drivers for frameworks I don't use or understand. One solution I can think of would be if a Commons commiter would volunteer to maintain that driver/interface and I could help them. The only other issue is that if the driver is in Commons then the example web apps and cactus unit tests would be there too. It doesn't seem like this should be there. Maybe that is just because there aren't any other Commons projects doing this yet, but there will be in the future.
David --- Ted Husted <[EMAIL PROTECTED]> wrote: > I'd say we need to build-in the Service Manager, and > then use the > Commons Validator as an standard example of how to > use it. > > Since the Commons Validator is designed as a > plug-in, I would lean > toward suggesting that it host its own "drivers". > This way if someone > finds a way to hook the validator up to framework X, > they can contribute > it to the Commons Validator, regardless of whether > framework X wants to > carry it or not. Having these together also works as > a very helpful > example for the next framework that wants to hook > up. > > Ditto for Tiles. It's designed to plug into other > frameworks, and it > seems to me it should then carry its own plugs. > > Since both David and Cedric are Struts committers, > so its just as easy > for them to commit the code here as there -- but > that's really just a > conincidence. A component is only as good as the > things it plugs into, > and these components need to control their own > destiny, and not rely on > the kindness of strangers. > > We can carry documentation in the User Guide > regarding how to use > Commons-Validator, Tiles, Velocity and whatever else > with Struts, and > I'll help write it, but I'm thinking the code level > interfaces really > belong with the components, and not so much with the > framework(s). > > -Ted. > > > David Winterfeldt wrote: > > Martin had mentioned in Commons whether or not to > move > > the Struts Validator interface out of commons and > into > > Struts proper. Any thoughts on this? It was on > the > > original 1.1 to do list to have a validation > framework > > built in. I could go either way, but I think it > would > > be nice if it was in the core. Especially since > there > > are so few classes left since most are in the > Commons > > now (6 classes plus one or two to be added for a > > ValidatorDynaActionForm). > > > > David > > > > __________________________________________________ > > Do You Yahoo!? > > Send FREE video emails in Yahoo! Mail! > > http://promo.yahoo.com/videomail/ > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
