Re: [Springframework-developer] Commons-Validator for Spring

[Seth L. <se...@eh...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Miller wrote:
| Seth and Keith,
|
| Did you get a chance to look at my commons-validator adaptor? I was
| wondering if you had any feedback? Feel free to tell me that it sucks, or
| that it was so elementary that you didn't want to waste any more time
| talking to me about it :)

Daniel,

I took a look at it briefly.  I think it's a wonderful idea.  It's also
nice because it will help prove the new interfaces being proposed for
the validation system.  I think your commons-validator should integrate
perfectly into the system as an option for validation.

|
| I don't know much about commons-attributes, but from what I've been
picking
| up between the lines on your recent validator-related posts it's quite
| different from the commons-validator approach. The main difference
seems to
| be that validation meta-data is expressed directly in the source of
the bean
| to be validated, while the commons-validator approach uses the
| validation.xml file to hold all of that meta-data.

That's correct.

|
| Your attributes validator sounds a bit more powerful than the commons
| validator, but many of the objects that I want to validate are
generated (by
| Middlegen) and I have no way of adding meta-data to the objects without
| modifying the generated code. Of course, I could just write a wrapper for
| each object that I want to validate, but I might as well just write a
| validator class for each object. That being said, I think there is
room for
| both an attributes validator and a commons validator in the Spring
| framework.

I agree.  I'm not sure either is more powerful, just different ways to
do it.  If they all follow the same interface(s), then it fits with the
Spring mindset.  Just choose a different implementation and let IoC wire
it up!

|
| The main thing I am interested in knowing is the patch that you (Seth)
| posted to allow message resources to be nested (as arguments) in another
| message resource. Do you have any idea how soon this will make its way
into
| a Spring release or should I just get the source and build it in for
my own
| use?

I think Keith is looking into that and hopefully we'll get something
added soon.

Looking forward to the options!
Seth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFASMYn5EIB1scRes8RAopIAJ4mnVTFnAVMevdtIgXWbrIYY8x1FACfSbJh
399P7qxijwtrUNELlxvFOtg=
=I9Wj
-----END PGP SIGNATURE-----