[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2980?page=c... ] Dobes Vandermeer commented on HHH-2980: --------------------------------------- Well, my main suggestion is to indicate more clearly which condition caused the error. I don't pretend to understand the source of the error, but removing a bunch of "FetchType.EAGER" from my class fixed it. I haven't personally found anything in the JPA spec that says that an EAGER mapping requires that the fetch be done in a single SQL query. It just seems to be talking about whether the objects are loaded immediately or on-demand. For collections I just thought this meant that the JPA provider had the option of providing a collection class implementation that lazily fetched the records instead of immediately fetching the collection's contents using a new (or simultaneous) query. It seem to me that if you issued multiple selects at the same time in order to fetch the collections, you might be able to get a queuing effect that reduces the effects of latency - e.g. I don't have to wait for the object to come back, then request the next one, I'd just request the object, request it's collections as the next result set(s) and then wait for the object, and then wait for each collection. I did notice that the JPA spec *does* *require* that implementation support EAGER fetching, and says that *LAZY* fetching should be taken as just a hint. That said, it's probably more applicable to NToOne and Basic columns. Personally, I'd rather have it just issue a warning, or just ignore the EAGER fetches, than throw an error, because this same class is accepted by other implementations without complaint, AND it's compliant to spec ... hibernate seems like the bad boy here - first for adding a constraint that isn't part of the spec, and second for reporting the error so, so poorly. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2980?page=c... ] Antoine Herzog commented on HHH-2980: ------------------------------------- Hi, it is true that the message is quite the minimum. and it is true that, when there is some help (such as : "you should put insertable=true, updatable=true..." or so...) it is great. Really great. well, anyway, for people who come to this Jira : here is a forum post that is very interesting about this issue. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=82946 There is both some (more) explaination of the problem, and some nice workaround ways. As Emmanuel says, it is not that simple... but there the explaination is nice... and the workaround seems to be good in most of the case. Hope it helps, -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2980?page=c... ] Steve Ebersole updated HHH-2980: -------------------------------- Assignee: Steve Ebersole Fix Version/s: 3.5 3.3.x 3.2.x Component/s: core I can offer adding a new exception type which captures the bag 'collection roles' (collection roles are the names of the collections in the form OwnerEntityName.collectionPropertyName). The message will remain the same, but the new type will expose a "Set/*<String>*/ getBagRoles()" method -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2980?page=c... ] Peter Centgraf commented on HHH-2980: ------------------------------------- What's the logic behind keeping the message non-useful? It seems reasonable to include the information from the VERY useful getBagRoles() as part of the message. -- 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