[hibernate-issues] [Hibernate-JIRA] Commented: (EJB-304) Multiple @OneToMany(fetch=FetchType.EAGER) realized by List not supported
[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-304?page=co...
]
Morten Andersen-Gott commented on EJB-304:
------------------------------------------
Hibernate Entitymanager doesn't adhere to the JPA specification. I believe this is a
bug that should be resolved in a manner that doesn't force the developer to abandon
the JPA specification and pursue a Hibernate specific solution.
What is the point of having the Hibernate Entitymanager product, if hibernate specific
annotations is the only way to use it?
Multiple @OneToMany(fetch=FetchType.EAGER) realized by List not
supported
-------------------------------------------------------------------------
Key: EJB-304
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-304
Project: Hibernate Entity Manager
Issue Type: Bug
Affects Versions: 3.2.0.cr1
Environment: JBoss4.0.4.GA
Reporter: Morten Andersen-Gott
Having more than one relationship on en entity annotated with
@OneToMany(fetch=FetchType.EAGER) causes exception when deploying the ejb3 module:
org.hibernate.HibernateException: cannot simultaneously fetch multiple bags.
This bug is thoroughly explained here:
http://www.jroller.com/page/eyallupu?entry=hibernate_exception_simultaneo...
and depends on HHH-1718 "Have multiple bag fetches revert to subselect fetching for
all but one of the bags"
The temporary solution in HHH-1413 - disallowing multiple bag fetches is unsuitable to
ejb3 environment, because the spec does not disallow it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira