commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Willingham" <>
Subject RE: validator & inheritance
Date Sun, 25 May 2003 17:01:25 GMT
Yeah, I've got to start working on it now and understand I'll have to
adapt to what changes you guys are making.  Would it be OK to discuss
what kind of work you guys are doing among us?  It would be nice to play
into each others hands in an efficient way.  Plus Im very curious too.
And I'd go over my approach with you guys too, or even follow a
recommendation if you're privy to that area of the code.

-----Original Message-----
From: Rob Leland [] 
Sent: Friday, May 23, 2003 10:14 AM
To: Jakarta Commons Developers List
Subject: Re: validator & inheritance

To add to what David said.

It sounds like you would find this useful, and it sounds very useful to 
me also, so....
I would say start working on it for yourself, work out the concepts, 
based on the
current --released-- validator source code. Just know that you'll likely

need to make changes to it
to work with the upcoming validator 1.1 release. My guess is that after 
doing a version for validator 1.0.1
source code you'll be able to suggest changes to the validator 1.1 that 
we haven't even thoughtt
of ! So go scratch that itch !!!


Christopher Willingham wrote:

>Are there are any wishes, hopes, or considerations for modifying the
>Validator by adding an extends attribute for inheritance, similar to
>tiles extends tile definitions?  I use the validator quite a bit; for
>EJB business logic edits, daemon feed edits, standalone edits, & also
>course struts.  Many of the core edit definitions for a particular
>entity type are the same with some variations.  In fact, within our
>webapp alone we run into situations where an edit suite for a form is
>nearly the same as another yet has a slight twist or difference, thus
>causing a repeat of many edit configurations under a different bean
>name.  Or perhaps there is something like that already built in(wishful
>If no work has been done in this area, I may consider adding such a
>feature if the community here also sees its advantage.  And would be
>willing to consider it for a future release.  If I get positive
>feedback, perhaps one of the original builders could point me in the
>right direction for approaching this task.  It doesn't seem like it
>would be extremely difficult.
>Please share your views!
>Chris Willigham

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

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

View raw message