Les Hazlewood wrote:
Whats wrong with doing:And give accurate info using log interface ?
public boolean isValid(Mapping mapping) {
try { validate(mapping); } catch (MappingException me) { return false; }
return true; }
No - isValid() should just return true and false as it does today ;)
validate(Mapping) whichi does NOT exist today - should throw the precise exception.
My question was more concerned on wether someone could find anything against having
the validate() close to the actual object being validating and have it throw an exception instead
of the way it works today.....and since noone objected to that i'll just make that change and see
what happens ;)
/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
