commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Cooper" <>
Subject Re: Commons Validator Packaging/Content
Date Sun, 06 Jan 2002 23:16:55 GMT
My take on this is that the Struts-specific code should be part of Struts.
Whether it should be a built-in or an add-on is a separate question, but we
can take that up on struts-dev (if other people agree that Struts is the
right place for it).

Martin Cooper

----- Original Message -----
From: "David Winterfeldt" <>
To: <>
Sent: Sunday, January 06, 2002 1:14 PM
Subject: Commons Validator Packaging/Content

> I've started committing the Validator to commons.  The
> core package doesn't have any dependencies except for
> some other commmons packages (beanutils, collections,
> digester).  There is currently a Struts
> interface/connector for the Validator.  I can see the
> benefit of having a good working example of the
> Validator in a real framework, but I'm not sure if it
> belongs in commons.  To compile the Struts interface,
> Struts and the Servlet API would need to be in the
> classpath.  I don't think any of the other commons
> packages have any dependencies outside of commons.  So
> the main question is whether the Struts related part
> belongs here as an example or it should be in Struts.
> What do others think?
> David
> __________________________________________________
> Do You Yahoo!?
> Send FREE video emails in Yahoo! Mail!
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message