>
>
>
> Hi Erik, et al.,
>
> "Ostermueller, Erik" wrote:
> >
> > I sure haven't seen anything like this,
> > Here is my wishlist for improvements in the validation framework.
> > I think my number 2 is similar to what you're requesting here.
> >
> > 1) Currently, when the validator encounters an exception, it punts right away
> (punt like in American football).
> > Instead, the validator should make an attempt to validate as much of the
> document/object as possible.
>
>
> You'll be happy to know much of the necessary code to make this happen
> is already available in Castor 0.9.5.3, ValidationContext has a way to
> override the fail-fast (though the validator itself currently ignores
> that) and validation exception supports linked list of exceptions.
> I just need to finish it up.
that's great news.
>
> >
> > 2) The code that uses castor should be able to programmatically inspect the
> validation errors.
> > Currently, if your code wants to know which element is 'broken',
> > you'll need to parse the english text of the validation exception (this is ugly).
> > It would be better to have an API that enumerated the errors via a data structure
> or something like that.
>
> +1 , I agree. If I provide you #1 above, would you or anyone else be
> willing to work on this item?
oh boy. Unfortunately, the project I'm working on now doesn't use castor,
so I have even less exposure to it than before.
That said, I'll see if I can find some time to throw together
a few loose design ideas for this.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
