Confusion between JPA and Hibernate cascading

Question

I\'m using Hibernate 3.6 and have my code annotated (versus using hibernate mapping files). I ran into the known \"problem\" of using JPA cascading options that are not com

Answer 1

This behaviour is documented in 11.11. Transitive persistence.

1. Hibernate cascade types correspond to the individual operations, so you need all three of them.

2. In most cases you need either CascadeType.ALL or no cascading at all. In that case JPA annotation is enough, since JPA's CascadeType.ALL covers all Hibernate operations as well. Otherwise, if you need fine-grained cascading control (and use Hibernate's Session interface), you need Hibernate's @Cascade.

3. It's not a bug in JPA implementation, because if you use JPA's EntityManager everything works fine. This problem exists only if you combine JPA annotations with Hibernate's Session interface.