Hi there

Actually I'm getting a very strange problem

I'm using JPA with Hibernate and DELETE_ORPHAN on @OneToMany relationships. Who makes my EntityManager and manages my transaction is Spring Framework.

I made some Unit/Integration tests and when I run they, everything works fine, exactly as I expected, even I use EXACLTY the configuration on web

but, when I use it on web, DELETE_ORPHAN doesn't work and I don't know what is happening. And other problem is, let's suppose this piece of code


As you can see, it's a common way to add/remove element on a relationship and, when I use merge() operation on EntityManager, my EntityManager must cascade the operations, right?

but I saw one crazy thing

if I execute this line

doesn't let my "element" object to be updated. In other words, if I change other property in "element" object, it won't update this property.
BUT, if I remove that line the "element" object will be updated

anybody got a similar situation like that?

I am not sure if I understand the problem correctly but if the only way an element is updated is through its parent then you can't expect the element to be updated if it is removed from its parent list. Therefore the behaviour you are seeing is the right behaviour. However, the element should be removed after the session flushes. Is that what is happening?


Farzad-

Exaclty, but the problem is: In the web environment my element isn't removed from database, but if I test in my TestNG tests, I do the same web configuration (with Spring, AOP Transactions and bi-injection).

In other words, like I did



and, after that, I do



DELETE_ORPHAN doesn't work, but ONLY in web environment :(

I did a lot of tests, but I did a work around to work on web, the same work-around that I did once, when I used to use Toplink JPA instead of Hibernate EntityManager. I'm using Hibernate with JPA (now) because Hibernate is better, there are some JPA extensions (like DELETE_ORPHAN and Criteria) that don't have on Toplink

Umm, there are two things I can think of. First, DELETE_ORPHAN does not work on unmanaged collections. This can be verified with the document. Second, the problem is somewhere in your transaction management. I mean probably your session does not get flushed to database. Well, to make things more clear, why dont you send us what you do in your tests and what you do in your web app. Maybe the comparison will point us to the problem.

This is very strange, because I have EXACTLY the same kind of transaction management in my TestNG Tests

I thought too about my unmanaged collections. But how can I manage they? In other words, maybe I have to do something special in web environment to transform my collections in managed

Ah, I forgot: My collection is a map collection with an enumeration as key