You can create your own validators in the xml file.
Just copy the required validator definition you are
using and have it point to your own method. Then you
could have the validation always return true if the
field doesn't exist in the request object.
validator name=conditionalRequired
Thanks for bringing it to my attention. I'll fix this
with what you gave me. My next step on the project
was documentation, but I've gotten sidetracked (big
project at work).
David
--- Jeff Linwood [EMAIL PROTECTED] wrote:
Hi,
I just built the commons validator from the
04/24/2002
I'm +1 on the mapper in commons. A
validation/transformation package would be very useful
to people. I haven't used it, but I looked at it a
little last night. There is some overlapping
functionality between the Validator and the Mapper,
but the Validator seems like it can do some things
that
--- Sam Ruby [EMAIL PROTECTED] wrote:
Jon Scott Stevens wrote:
on 1/6/02 1:14 PM, Sam Ruby [EMAIL PROTECTED]
wrote:
David Winterfeldt wrote:
I don't think any of the other commons
packages have any dependencies outside of
commons.
3 depend on log4j, 2 depend on servletapi, 1
The Validator's core validation has been stand-alone
and independent of Struts for about 6 months when it
was refactored to completely decouple it from Struts.
The project itself is over a year old and was based on
production code that is even older. So this code has
been in production for a
I had started on auto-generating classes based on a
database table as a proof of concept, but I haven't
worked on it anymore since I found out it about
Torque, Castor, etc. I liked the idea of keeping
things very simple and generating jdbc code that you
would have written yourself so it would be
over, as was done
with BeanUtils,
Collections, and the Digester.
David has been an active Struts committer for some
time, and so
breveting him as a Commons committer is easy enough.
David Winterfeldt wrote:
This validation framework was made to work with
Struts
originally
