If someone can point me in the right direction I would be very appreciative.

@Version not working as I expected with cascade saving.

I have 2 classes: PARENT_CLASS and CHILD_CLASS.

PARENT_CLASS contains a set of CHILD_CLASS.

Both class PARENT_CLASS and CHILD_CLASS have a field annotated @Version.

If I call merge() on either PARENT_CLASS or CHILD_CLASS their respective version number is incremented.

However, if I add a new instance of CHILD_CLASS as a child to an instance of PARENT_CLASS and then call merge() on parent instance, the version number for the PARENT_CLASS is incremented, but the CHILD_CLASS version is inserted into the database as 0 when the merge is cascaded to the child.

What should it be by your opinion / or what's the problem?
Isn't 0 correct since child is a new instance?

I think the problem is my fault!

0 is the version assigned to a new instance - and is working fine - i had just misunderstood the numbering.

I am still a little confused though. I have the following scenario.

1. I create a new child (with a reference to the parent). save it to the database and it is given version == 0. I have not saved the parent yet.
2. I save the parent with the child in it's set. Now the child in the database has a version number == 3.

Why does the version jump from 0 to 3?

Repeat the same scenario with sql logging turned on.
Look for updates on this child instance.