Folks,

I tried to insert a new record (with two many-to-one associations, first one is a pure simple many-to-one association, second one is within a component). However, it looks like the setting cascade="none" has no effect on the second many-to-one association (i.e. one within the component) and Hibernate generates the TransientObjectException, any ideas?

P.S.
The first many-to-one association works fine (with cascade="none" too) which Hibernate would ignore it during the insert.

Thanks in advance!

Martin

Hibernate version:
2.1.6

Mapping documents:


Code between sessionFactory.openSession() and session.close():


Full stack trace of any exception that occurs:



Name and version of the database you are using:
Oracle 8.1.7

Debug level Hibernate log excerpt:

When you define a component, it means you have a relationship with an value object. This means the lifcycle of your entity and the value object are the same. So in this case it makes no sense to define a many-to-one relationship or to define a cascade = none. From this point it makes sense when it ignores the cascade in a component.

Reto

Thanks for your reply, any suggestion to ignore the many-to-one assoication within the component during insert/update/delete?