new in 2.1beta5: NullPointerException

jkristian · **Posted:** Thu Oct 30, 2003 9:17 pm

Hibernate 2.1beta5 validates not-null properties more thoroughly. For example, an application test case (which passed with 2.1beta4) fails thus:

Code:

java.lang.NullPointerException: not-null property references a null or transient value: manager
at net.sf.hibernate.impl.SessionImpl.nullifyTransientReferences([Ljava.lang.Object;[Lnet.sf.hibernate.type.Type;ZLjava.lang.Object;[Z[Ljava.lang.String;)V(SessionImpl.java:900)
at net.sf.hibernate.impl.SessionImpl.doSave(Ljava.lang.Object;Ljava.io.Serializable;Z)Ljava.io.Serializable;(SessionImpl.java:803)
at net.sf.hibernate.impl.SessionImpl.save(Ljava.lang.Object;)Ljava.io.Serializable;(SessionImpl.java:682)
etc...

Removing an erroneous not-null attribute from my mapping file yielded better results.

gavin · **Posted:** Fri Oct 31, 2003 12:48 am

Yup, its true.

This is a good thing, I think :->

Should I throw some other exception than NPE? No, I think NPE is best.

jkristian · **Posted:** Fri Oct 31, 2003 1:33 pm

TransientObjectException would be a better choice, in the case of a property that refers to a transient object. I propose http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-442

max · **Posted:** Sun Nov 02, 2003 1:50 pm

If it can refer a non-null object (in form of another object instance) then NPE sounds "wrong".

IllegalStateException and IllegalArgumentException sounds more "liable" .......