#562 ✓wontfix
Leif Gensert

JPA's @ElementCollection and Fixtures don't seem to work

Reported by Leif Gensert | January 26th, 2011 @ 07:40 AM | in 1.3 (closed)

Helle everyone,
I wrote a project using the @ElementCollection (which provides an easy
way to persists Lists and Maps to a database).
I still want to use the Fixtures engine used in play. It's easy to
declare maps in yml format. This works as well. But when I have other
children using the @ManyTonOne annotation the problems start.
As long as only 1 parent entity is declared in the data.yml everything
is fine. As soon as a child to another parent entity is created a
HibernateException is thrown:
A java.lang.RuntimeException has been caught, Cannot load fixture
data.yml: org.hibernate.HibernateException: Found two representations
of same collection: models.CollectionHolder.genericParameters
To illustrate the problem, I provided a small sampleproject on github:


Just run the unit test and the error occurs. In the data.yml you'll
find a comment. If you delete all the lines underneath the comment,
the test runs fine.

This was all tested with the latest 1.2 version on MacOS X 10.6.6 and Windows XP

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.

People watching this ticket