> the problem i'm having 
      > is that the 
      > validation
      > code seems to be somewhat simplistic.  the only way i 
      > know what went 
      > wrong is
      > to view the message in the ValidationException object.  
      > what i want is 
      > to be
      > able to determine programmatically the cause of the 
      > validation error.  
      > how can
      > i inspect this object to determine, for example, that it didn't 
      > validate
      > because the _condiment field is null but is required to 
      > be set to 
      > something
      > since minOccurs is 1?
I haven't seen anything like this.  However, various people on the list
have made a number of suggestions for enhancing the error reporting.
Perhaps we should start organizing our wish-list for this.

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-dev

Reply via email to