Should we not make a validate(Mapping) on property and value which throws appropiate exceptions (especially with a more precise message) the the current on in ClassPersister which just call's isValid() and assumes it has soemthing to do with number of columns....
Any reasons/arguments against having validate(Mapping) throws MappingException instead isValid(Mapping) that just return true/false ? (we could implement isValid(Mapping) in terms of validate(Mapping).
/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
