:: 1) Nobody (that i see in these threads) directed that :: comment at you, so take it easy. :: 2) Not sure how much more descriptive the error message :: could get; you tried to specify a type mapping between a :: java primitive value and a database column that contained :: null values. In java, primitive types cannot hold null :: values (really, its true, check it out). If the column can :: contain null values, use a primitive wrapper type.
"Since then I've read the faq entry" :) I'm not an idiot, I'm just overloaded and sent a bug report right on when I've seen that it came from the depth... But I admit I was a little slow on this. If you want to avoid the need for a faq entry for this you should check for this at configuration time and issue a warning (primitive type + not-null="false"). Not to mention that it can delay the appearance of the bug, so it can help slip it out for production releases. But at the very least: throw new PropertyAccessException(npe, "Null value was assigned to a property of primitive type (check your mappings for nullable properties mapped to primitive types)", true, clazz, propertyName); I need some rest. Thanks, - 101 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id149&alloc_id66&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
