#1395 ✓resolved
Martin Gontovnikas

OrphanRemoval bug in OneToMany relations in Play!

Reported by Martin Gontovnikas | January 27th, 2012 @ 03:41 AM | in 1.2.5 (closed)

I have a relation of OneToMany that I don't want it to be

The relation is:


@OneToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY,

orphanRemoval= true)

@JoinTable( name = "ProductItemForProduct", 
            joinColumns = @JoinColumn(name = "productId"), 
            inverseJoinColumns = @JoinColumn(name =


            uniqueConstraints = @UniqueConstraint(name =

"uq_productItemPerProduct", columnNames = {

                    "productId", "productItemId"})) 
public Set<ProductItem> items = Sets.newHashSet();

The problem is that I'm getting an error each time that I edit the
"org.hibernate.HibernateException: A collection with cascade="all- delete-orphan" was no longer referenced by the owning entity instance"

So I started to debug code, and the problem is that Play JPA plugin
when does the binding of a OneToMany relation, it creates a new
HashSet and then it fills it with the elements ans assign it to the
parent object. That's precisely the problem.
If we use orphanRemoval, Hibernate needs the Collection NOT to be set
again, and to be modified the one that exists. You can either clear it
and add all of the elements again. If I don't set the orphanRemoval,
the ProductItem table increases exponentially.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.