I have a relationship that looks something like this:



I'm finding that no matter what cascade options I set, I still get a "org.hibernate.PropertyValueException: not-null property references a null or transient value: blah.Child.parent" exception.

Is there some way to make it work? There don't appear to be any examples exactly like this in the documentation. I want, when Parent is created, for there always to be one instance of Child created along with it.

Thanks in advance,
Jeff

I recently worked on this. I was able to save parent child.
Please post your hbm configuration file. and also you need to have inverse=true in the parent cfg.

There isn't a hbm config file - this is using the EJB3 system under JBoss. My example in this topic pretty much included all of the relevant content. Note that mappedBy is the equivalent of inverse="true".

However, if you want to see the real deal, here is the Parent object:

http://subetha.tigris.org/source/browse ... cvs-markup

Here is the child object:

http://subetha.tigris.org/source/browse ... cvs-markup

There are three relationships:

ManyToOne from Role to MailingList
OneToMany from MailingList to Role (being mappedBy, this is the equivalent of "inverse")
OneToOne from MailingList to Role (the default role)

Both the ManyToOne and OneToOne relationships are nullable=false.

The constructor of MailingList (the parent) must create, and include for persistence, a single default role.

Thanks,
Jeff Schnitzer

I think if you change

to


it will work. In the majority of cases, both sides of a bi-directional association should be set explicitly.

My mistake when creating the example - yes, in fact, I am setting both sides of the bidirectional association. You can see it in the actual code linked above. Still produces an exception.

I think the extra OneToOne relationship is confusing hibernate in some way. I'll have to narrow down a test case.

Thanks,
Jeff Schnitzer