Hello,
I've read the docs and browsed the forums and still can't figure out this one:

I have a Parent and a Child in a one-to-one relationship, sharing the ID, which is actually created first in the Child object.
When I save the parent, it inserts the parent and then tries an update on the child (not yet inserted)...
///////////////////////////////////
Here is what I'm trying to do:

Session session = HibernateUtil.currentSession();
Transaction tx = session.beginTransaction();

Parent p = new Parent();
p.setName("parentName");
Child c = new Child();
c.setObjectId("user1");
c.setName("childName");
c.setParent(p);
p.setChild(c);

session.save(p);

tx.commit();
HibernateUtil.closeSession();

////////////////////////////////////
My config goes like:
<class
name="xpetstore.domain.Parent"
table="T_PARENT"
>
<id name="objectId">
<generator class="foreign">
<param name="property">child</param>
</generator>
</id>

<one-to-one
name="child"
class="xpetstore.domain.Child"
cascade="all"
/>
<property
name="name"
type="java.lang.String"
column="name"
length="20"
not-null="false"
unique="false"
/>
</class>

<class
name="xpetstore.domain.Child"
table="T_CHILD"
>
<id name="objectId">
<generator class="assigned"/>
</id>

<property
name="name"
type="java.lang.String"
column="name"
length="20"
not-null="false"
unique="false"
/>
</class>
///////////////////////////////////////
Note.
right now in class Parent: getObjectId() returns getChild().getObjectId()...

I have tried several ways to do the cascade save but no chance yet.
I would deeply appreciate any help or directions on this one.
Thanks a lot again

Gilles

Since you child has an assigned generator, you manually set a non null id, then Hibernate try to update it. It applies the saveOrUpdate strategy. The easiest solution is to manually save the child before saving the parent.
Have a look at the reference guide and http://www.hibernate.org/116.html#A11 for a list of solutions.

Thanks Emmanuel,

I'm actually looking for a way to do it with just one "smart" save, would you know what could force the session.save(p) to save the child first?
I've got cascade="all", constrained="true" from Parent.
The one-to-one are now:
Parent:
<one-to-one
name="child"
class="xpetstore.domain.Child"
cascade="all"
constrained="true"
/>

Child:
<one-to-one
name="parent"
class="xpetstore.domain.Parent"
/>

I can't find any example that's close to my scenario.

Thanks again
Gilles

The cascaded and constrained stuff plus using unsaved-value="any" in the child id would do the work.

Child will be saved instead of updated, and parent will be saved after child.

thank you , thank you, thank you...

the unsaved-value was my mistake...
back to documentation, I guess...

thanks a lot Emmanuel
Gilles