Max Rydahl Andersen wrote:
Emmanuel wrote:OK, but when using isValid() which is the only available today, you will swallow the exception to return false, as per the code Les showed. So I don't see any useful usage, you lost the information/exception.
What was your point, giving accurate infos in log before the return false ?
My intention was to provide the accurate info's in the exception it self. Right now
the message assumes it's the same one of three possibilities.
/max
To have a good info, you'll have to update places where isValid(Mapping) is used and rethrown as a MappingException("Wong nbr of column") and just call validate(Mapping). If it's your point then it's fine
Yes - that is my point, and as isValid() is only called once then it's pretty easy to handle ;)
/max
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
