good idea. I dumped it onto the castor wiki. http://www.brainopolis.com/castorwiki/Wiki.jsp?page=ValidationFrameworkWishList
-----Original Message----- From: Stein M. Hugubakken [mailto:[EMAIL PROTECTED] Sent: Thursday, April 15, 2004 11:01 AM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] ValidationException : how to determine exact XML data error 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. > > 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. > > 3) i18n. the sol'n must enable multiple language versions of the a single > validation error. > This solution could be built on top of the above item (2). I think rendering > the message into a particular language could be (and should be) easily be separated > from the validation framework. > > Erik, You should add this to bugzilla so it won't be forgotten. Stein ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
