Hibernate one-to-one not-null property references a null or transient value

These old forums are deprecated now and set to read-only. We are waiting for you on our new forums! Page 1 of 1 [ 3 posts ] Previous topic Next topic Author Message Adry Post subject: not-null property references a null or transient value Posted: Wed Jun 27, pm.

Hibernate version: 2. Try the following: 1 For each stone, set its road i. When you set items, you need to loop through the set and call item. If you implement an addItem method, you need to do the same thing. Or you need to otherwise set the Invoice of every InvoiceItem in the collection. If you have automated ID creation by hibernate framework and you are setting the ID somewhere it will throw this error.

By default the unsaved value is 0, so if you set the ID to 0 you will see this error. I was getting the same error but solved it finally,actually i was not setting the Object Entity which is already saved to the other entity and hence the Object value it was getting for foreeign key was null.

So the relation is to itself. Let make the child menu:. Thus, the relation is Many To One. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. These old forums are deprecated now and set to read-only. We are waiting for you on our new forums! Page 1 of 1 [ 7 posts ] Previous topic Next topic Author Message zaghdoudi Post subject: not-null property references a null or transient value. Posted: Wed Oct 20, am. It appears that the PAGER value comes in as an Empty String and somewhere in the Hibernate codes saves it as a null so it thinks it's dirty and tries to write that back out.

I dumped some of the log records that show the same type of behavior. Does this look like a bug in Hibernate? Oh ya, here's a segment of the stacktrace with the check for null in the POJO. Exception at com. Posted: Sun May 21, pm. Weird that the only time setPager null was called was during the session factory creation, almost a full second before your first select.

I'm not certain that the empty pager value that we see in the parameter tracing is in any way related to the stack trace. Do you know why a VoicemailUsers object is being created at that point? And more importantly, why is an object that hibernate created without going to the database being later saved to the database? I guess I'm missing something, but I can't figure out why we're seeing output like that. Posted: Mon May 22, pm. I suspect the empty pager value that we see is happening when Hibernate is using reflection to see what the POJO looks like and not actually when it's creating record objects.

I think what we might be seeing is a bug in how hibernate deals with XML. If the string is empty, it can't tell if it's null or empty. Just removing the not-null from your Pager property should address the issue.

Hibernate seems to go through the movements to check which objects are clean and appears to be stumbling across those with null values. And your assessment is correct that Hibernate would have difficulties distinguishing between "" and NULL. More precisely, in most databases you are going to find that "" is treated as NULL. Posted: Tue Jun 20, pm.