Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-05-06 15:33:29
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1537?page=comments#action_23031 ] Emmanuel Bernard commented on HHH-1537: --------------------------------------- well actually did not solve my problem > Configuration.addInContext(String, Object) > ------------------------------------------ > > Key: HHH-1537 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1537 > Project: Hibernate3 > Type: New Feature > Components: metamodel > Reporter: Emmanuel Bernard > Priority: Minor > > > Would be cool to have that, The Initializable event listener scould get some information from here, not only properties. > the drawback is that the user have to handle the Configuration creation programmatically which kinda limit it in EJB3 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-05-06 15:31:23
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1537?page=all ] Emmanuel Bernard resolved HHH-1537: ----------------------------------- Fix Version: (was: 3.2.0) Resolution: Rejected Last time I remember thinking about that, it was a bad idea > Configuration.addInContext(String, Object) > ------------------------------------------ > > Key: HHH-1537 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1537 > Project: Hibernate3 > Type: New Feature > Components: metamodel > Reporter: Emmanuel Bernard > Priority: Minor > > > Would be cool to have that, The Initializable event listener scould get some information from here, not only properties. > the drawback is that the user have to handle the Configuration creation programmatically which kinda limit it in EJB3 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Alexander R. (JIRA) <no...@at...> - 2006-05-06 14:57:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-9?page=comments#action_23029 ] Alexander Rupsch commented on ANN-9: ------------------------------------ Is this ported to beta10? If not, will it be in the near future? regards > Support interface inheritance mapping > ------------------------------------- > > Key: ANN-9 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-9 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Versions: 3.1beta3 > Reporter: Gili > Attachments: hibernate3-annotations-3.1beta5-3896-3948.diff, hibernate3-annotations-3.1beta5-3896-4138.diff > > > It should be possible to create a mapping with interfaces, as described by the documentation here: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#inheritance-tableperclass > Specifically right now it is impossible to annotate interfaces and according to HBX-231 even if you could @Entity is only meant to get used on classes so the question becomes "what do you annotate it with?" > As I pointed out here http://forum.hibernate.org/viewtopic.php?p=2238824#2238824 the additional problem seems to be that XDoclet doesn't support interface annotation either (http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1345) so I'm left without a workaround. > I can't convert the interfaces to abstract classes because I implement multiple interfaces in my application and Java does not do multiple inheritance. > If you know of a nice workaround, please let me know :) -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Sergey V. (JIRA) <no...@at...> - 2006-05-06 10:00:26
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-870?page=comments#action_23028 ] Sergey Vladimirov commented on HHH-870: --------------------------------------- Max, I'm sure you need to make it an optional. For example, my application knwo when to clear caches, and when just remove one entity from the cache. So, please, make an option to disable clearing all caches. But clearing all caches should be default behavior for sql update queries, IMO. > support SQL updates in named queries > ------------------------------------ > > Key: HHH-870 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-870 > Project: Hibernate3 > Type: New Feature > Components: core > Environment: Hibernate 3.0.5, SQL Server 2000 > Reporter: Nathan Moon > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 3.2.0.cr2 > Attachments: NativeSQLQueryPlan_withNamedParameters.java.txt, patch.txt > > > currently attempting to execute a named <sql-query> that is an update statement throws java.lang.UnsupportedOperationException: Update queries only supported through HQL. > In order to execute sql updates, the Session.connection() must be used directly. > (see forum topic http://forum.hibernate.org/viewtopic.php?t=940281) > It would be very nice to be able to be able to externalize SQL update statements and be able to run them with Session.getNamedQuery(). -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-05-06 07:37:23
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724?page=comments#action_23027 ] Max Rydahl Andersen commented on HHH-1724: ------------------------------------------ Correction: It does know what the underlying field type is; just need to add the same logic for the various operations. > Critieria needs to be aligned with new aggreation type rules > ------------------------------------------------------------ > > Key: HHH-1724 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr2 > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 3.2.0 > > > Criteria does not ask the dialect about the type + it does not always seem to know what the underlying field type is..... > created as blocker to make sure we either document or fix 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-05-06 07:35:24
|
Critieria needs to be aligned with new aggreation type rules
------------------------------------------------------------
Key: HHH-1724
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.cr2
Reporter: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.2.0
Criteria does not ask the dialect about the type + it does not always seem to know what the underlying field type is.....
created as blocker to make sure we either document or fix 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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Max R. A. (JIRA) <no...@at...> - 2006-05-06 07:09:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-870?page=comments#action_23026 ] Max Rydahl Andersen commented on HHH-870: ----------------------------------------- yes 2nd level cache eviction. It is the exact same code/behavior that happens when you use hql bulk manipulation - only difference is that we actually always know which entities/collections that are affected. I'm just curious on what the spec says regarding such issues. Should we just let the user shoot him self when doing native sql updates through hibernate and only help him if he uses <synchronize> which AFAIK is not possible via ejb3. > support SQL updates in named queries > ------------------------------------ > > Key: HHH-870 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-870 > Project: Hibernate3 > Type: New Feature > Components: core > Environment: Hibernate 3.0.5, SQL Server 2000 > Reporter: Nathan Moon > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 3.2.0.cr2 > Attachments: NativeSQLQueryPlan_withNamedParameters.java.txt, patch.txt > > > currently attempting to execute a named <sql-query> that is an update statement throws java.lang.UnsupportedOperationException: Update queries only supported through HQL. > In order to execute sql updates, the Session.connection() must be used directly. > (see forum topic http://forum.hibernate.org/viewtopic.php?t=940281) > It would be very nice to be able to be able to externalize SQL update statements and be able to run them with Session.getNamedQuery(). -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:50
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve this. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:50
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1552?page=all ] Steve Ebersole updated HHH-1552: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > Error when using ?1 and parameterList > ------------------------------------- > > Key: HHH-1552 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1552 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.alpha1 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Fix For: 3.2.0 > > > select item from Item item where item.name in ( :n ) > query.setParameterList("n", list); works > select item from Item item where item.name in ( ?1 ) > query.setParameterList("1", list); > raise an exception > java.lang.NullPointerException > at org.hibernate.hql.ast.ParameterTranslationsImpl.getNamedParameterSqlLocations(ParameterTranslationsImpl.java:59) > at org.hibernate.loader.hql.QueryLoader.getNamedParameterLocs(QueryLoader.java:458) > at org.hibernate.loader.hql.QueryLoader.bindNamedParameters(QueryLoader.java:481) > at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1577) > at org.hibernate.loader.Loader.doQuery(Loader.java:661) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) > at org.hibernate.loader.Loader.doList(Loader.java:2145) > at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029) > at org.hibernate.loader.Loader.list(Loader.java:2024) > at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:375) > at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:333) > at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) > at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1105) > at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) > Note that select item from Item item where item.name = ?1 > works like a charm -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:50
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole updated HHH-1543: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > query cache and fetches > ----------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. > Same for entity fetches. > Same for cached criteria query results -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:50
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1217?page=all ] Steve Ebersole updated HHH-1217: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > Problems loading lists of scalar values via EntityMode.DOM4J > ------------------------------------------------------------ > > Key: HHH-1217 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1217 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.5 > Environment: HIbernate 3.0.5, MySql 4.10 (Innodb), Windows XP > Reporter: Patrick Casey > Fix For: 3.2.0 > > > Mappings which contain lists of scalar values (as opposed to lists of mapped objects) throw NPEs when you try to load them via a DOM4J session. > **The Mapping: > <class name="metadata.MetaFormDescriptor" table="metaform"> > <cache usage="read-write" /> > <id name="id" type="string" length="32"> > <column name="id" length="32" not-null="true"/> > <generator class="uuid.hex"/> > </id> > <property name="objectClass" column="objectclass" type="string"/> > <many-to-one name="user" class="core.User" embed-xml="false"> > <column name="user_id" length="32"></column> > </many-to-one> > <list name="listA" table="mfa" fetch="join" cascade="all-delete-orphan" embed-xml="false"> > <key column="form_id" /> > <index column="sequence" /> > <element type="string" column="encoded"/> > </list> > <list name="listB" table="mfb" fetch="join" cascade="all-delete-orphan" embed-xml="false"> > <key column="form_id" /> > <index column="sequence" /> > <element type="string" column="encoded"/> > </list> > <list name="listC" table="mfc" fetch="join" cascade="all-delete-orphan" embed-xml="false"> > <key column="form_id" /> > <index column="sequence" /> > <element type="string" column="encoded"/> > </list> > </class> > **The Code that Loads it: > Session sxml = snormal.getSession(EntityMode.DOM4J); > sxml.setFlushMode(FlushMode.NEVER); > List l = sxml.createQuery("from " + MetaFormDescriptor.class.getCanonicalName()).list(); > ** The Dump you get: > Exception in thread "main" java.lang.NullPointerException > at org.dom4j.tree.AbstractElement.addElement(AbstractElement.java:1169) > at org.hibernate.collection.PersistentIndexedElementHolder.readFrom(PersistentIndexedElementHolder.java:135) > at org.hibernate.loader.Loader.readCollectionElement(Loader.java:674) > at org.hibernate.loader.Loader.readCollectionElements(Loader.java:370) > at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:314) > at org.hibernate.loader.Loader.doQuery(Loader.java:412) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:218) > at org.hibernate.loader.Loader.loadCollection(Loader.java:1434) > at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:99) > at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:488) > at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) > at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1430) > at org.hibernate.type.CollectionType.getCollection(CollectionType.java:484) > at org.hibernate.type.CollectionType.resolveKey(CollectionType.java:332) > at org.hibernate.type.CollectionType.resolve(CollectionType.java:326) > at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:105) > at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:530) > at org.hibernate.loader.Loader.doQuery(Loader.java:436) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:218) > at org.hibernate.loader.Loader.doList(Loader.java:1593) > at org.hibernate.loader.Loader.list(Loader.java:1577) > at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:395) > at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:271) > at org.hibernate.impl.SessionImpl.list(SessionImpl.java:844) > at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74) > at bootstrap.PrimeMover.unLoadOneFile(PrimeMover.java:41) > at bootstrap.PrimeMover.unLoadSeed(PrimeMover.java:59) > at zzTest.Tester.main(Tester.java:736) -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:49
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1537?page=all ] Steve Ebersole updated HHH-1537: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > Configuration.addInContext(String, Object) > ------------------------------------------ > > Key: HHH-1537 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1537 > Project: Hibernate3 > Type: New Feature > Components: metamodel > Reporter: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.0 > > > Would be cool to have that, The Initializable event listener scould get some information from here, not only properties. > the drawback is that the user have to handle the Configuration creation programmatically which kinda limit it in EJB3 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:48
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1709?page=all ] Steve Ebersole updated HHH-1709: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > Be able to raise ENFE rather than LIE in proxies > ------------------------------------------------ > > Key: HHH-1709 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1709 > Project: Hibernate3 > Type: New Feature > Components: core > Reporter: Emmanuel Bernard > Fix For: 3.2.0 > > > For HEM and EJB3 -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:48
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1039?page=all ] Steve Ebersole updated HHH-1039: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > WrongClassException when scrolling through EntityMode.DOM4J and loading identical objects from different fields > --------------------------------------------------------------------------------------------------------------- > > Key: HHH-1039 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1039 > Project: Hibernate3 > Type: Bug > Versions: 3.0.5 > Environment: Windows XP, JDK 1.4.2_8, Hibernate 3.0.5, Oracle 9.2. Replicated on Windows XP, JDK 1.5.0_2, Hibernate 3.0.5, MySQL > Reporter: Roland Groen > Fix For: 3.2.0 > Attachments: HbmXmlTest.java, Test.hbm.xml > > > When working with XML representations of entities, an unexpected org.hibernate.WrongClassException is thrown when working with identical embedded objects (embed-xml="true") which have different field names. > org.hibernate.WrongClassException seems to be thrown when: > 1) Running in EntityMode.DOM4J > 2) Scrolling through a result set using session.scroll() > 3) Embedding objects that are: > a) Referred by least by one of the objects on which the query is selecting primarily (parent object) and, > b) that field is in FetchMode.JOIN. > c) Referred by one object which is embedded (embed-xml="true") and uses a different field name to refer to the object than the parent object. > I would like to apologise for the large test case. The bug is quite hard to reproduce, I tried to minimise the test, but this seems the smallest and most simple case I can find. > The stack trace is: > Caused by: org.hibernate.WrongClassException: Object with id: 1 was not of the specified subclass: Customer (loaded object was of wrong class) > at org.hibernate.loader.Loader.instanceAlreadyLoaded(Loader.java:890) > at org.hibernate.loader.Loader.getRow(Loader.java:846) > at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:305) > at org.hibernate.loader.Loader.loadSingleRow(Loader.java:238) > at org.hibernate.impl.ScrollableResultsImpl.prepareCurrentRow(ScrollableResultsImpl.java:477) > at org.hibernate.impl.ScrollableResultsImpl.next(ScrollableResultsImpl.java:106) > at HbxXmlTest.main(HbxXmlTest.java:90) > The included files are: > Test.hbm.xml : the hbm file to create the classes > HbmXmlTest.java : the the java source to reproduce the issue. > Greetings, > Roland. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:36
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050?page=all ] Steve Ebersole updated HHH-1050: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > HQL Unions > ---------- > > Key: HHH-1050 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050 > Project: Hibernate3 > Type: New Feature > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.0 > > > Add the ability to define unions in HQL. Support will be initially limited to only: > 1) scalar queries : select id from Animal union select id from Car > 2) the same entity : from Animal where ... union from Animal where ... > Support both UNION and UNION ALL -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:30
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1083?page=all ] Steve Ebersole updated HHH-1083: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > Customization of CREATE TABLE with storage clause etc. > ------------------------------------------------------ > > Key: HHH-1083 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1083 > Project: Hibernate3 > Type: New Feature > Reporter: Christian Bauer > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > Currently Hibernate features a hotfix for the MySQLInnoDBDialect: > public String getTableTypeString() { > return " type=InnoDB"; > } > However, this is not the only appendix that is useful for CREATE TABLE. We should do several things: > - allow appendix for CREATE INDEX, for example, to define the tablespace > - pass in additional arguments to getTableTypeString(), such as tableName, schemaName, catalogName - for example, to allow custom Dialects to return different tablespaces for particular tables > - probably rename the getTableTypeString() method to getTableAppendixString() and getIndexAppendixString() -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:28
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=all ] Steve Ebersole updated HHH-422: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2.0 > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > I'm sure someone else is already in the process of agnonizing over how to handle the entity name resolution issues that are currently floating around in the codebase, but for the sake of not knowing who's doing what and what-not (heh), I thought I would share my couple quick notes learned from trying to make this work today. > I was having problems getting an import of xml data into hibernate with derived subclasses of one base class. (Not abstract, derived using the discriminator value column and table per subclass method). Was getting lots of errors trying to map my subclass nodes into the main xml document, even if I named the child nodes the same as the parent. The only eventual temporary solution I could find was by adding the subclass "node name" values into the two Map instances I could find that needed these references. [Mappings class and EntityPersister, ughh I've forgotten the other ones name now. ] > The one main culprit already had an obvious method comment with a TODO tag so I'm sure someone is already working on a much better longterm solution than mine.. The only thing I didn't complete was having the ability for the subclass instances to have their own node names. Ie if I had an instance of the base class mapped as a many-to-XX collection in someone's class, I had to specify a node name of "something" to get it to be recognized. I didn't get far enough in my day to get this part as well, but I think it would just require being able to reference the current child somehow. Some sort of XSLT expression like "name()" or "self" perhaps? > After that everything worked beautifully of course :) Will be very excited to see this feature come to full bloom, as I plan on using it to synchronize some data points with customer databases sometime this summer? (Am I being too hopeful? I'd love to help, but I'm sure there are plenty of good people doing things already..And I'm I'm fu#$!@ with my own deadlines anyways...) -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:27
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-616?page=all ] Steve Ebersole updated HHH-616: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > replicate() with a bidirectional relationship fails (dom4j) > ----------------------------------------------------------- > > Key: HHH-616 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-616 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.5 > Environment: Hibernate 3.0.5; MySQL 4.1.12 > Reporter: David Tashima > Assignee: Gavin King > Fix For: 3.2.0 > Attachments: test.zip, test3.zip > > > Here is the original forum post: > http://forum.hibernate.org/viewtopic.php?t=943520 > Basically, I am trying to transfer stuff from one DB to another via the Dom4j session. I create an XML document from the source DB and then I am using session.replicate() on the receiving end to instantiate the new objects from that XML document. > It works for simple objects, but when I have a bidirectional reference, it is unable to .replicate() the pair of objects, even if I try to commit() them all in the same transaction. > I have created a simple model to reproduce this. > Mapping document: > <hibernate-mapping > package="data"> > <class name="Foo" > table="foo" > > > <id name="id" > node="@id" > type="string" > unsaved-value="null" > column="foo_id" > > <generator class="uuid" /> > </id> > <property > name="prop1" > column="prop1" > type="string" > /> > <many-to-one > name="bar" > column="bar_id" > class="Bar" > not-null="false" > embed-xml="false" > /> > <property > name="index" > column="foo_index" > type="int" > update="true" > /> > </class> > <class name="Bar" > table="bar" > > > <id name="id" > node="@id" > type="string" > unsaved-value="null" > column="bar_id" > > <generator class="uuid" /> > </id> > <list > name="foos" > node="foos" > embed-xml="true" > inverse="true" > lazy="false"> > <key column="bar_id"/> > <list-index column="foo_index"/> > <one-to-many > class="Foo" > embed-xml="false" > node="foo" > /> > </list> > </class> > </hibernate-mapping> > Reconstitution code: > try > { > SAXReader reader = new SAXReader(); > Document doc = reader.read(new File("content.xml")); > Session session = currentSession(); > Session s = session.getSession(EntityMode.DOM4J); > Transaction txn = s.beginTransaction(); > { > List elems = doc.getRootElement().elements(); > Iterator it = elems.iterator(); > while(it.hasNext()) > { > Element e = (Element)it.next(); > log.debug(e.getName()); > if(e.getName().equals("Foo")) > s.replicate("data.Foo",e, ReplicationMode.IGNORE); > if(e.getName().equals("Bar")) > s.replicate("data.Bar",e, ReplicationMode.IGNORE); > } > } > txn.commit(); > } > catch(DocumentException e) > { > log.error(e); > } > Here is the stack trace: > 150 [main] ERROR org.hibernate.util.JDBCExceptionReporter - Cannot add or update a child row: a foreign key constraint fails > 291 [main] ERROR org.hibernate.event.def.AbstractFlushingEventListener - Could not synchronize database state with session > org.hibernate.exception.ConstraintViolationException: could not insert: [data.Foo] > at org.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:74) > at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) > at org.hibernate.persister.entity.BasicEntityPersister.insert(BasicEntityPersister.java:1869) > at org.hibernate.persister.entity.BasicEntityPersister.insert(BasicEntityPersister.java:2200) > at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:46) > at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:239) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:223) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:136) > at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:274) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:730) > at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:329) > at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:86) > at Test.reconstitute(Test.java:69) > at Test.main(Test.java:40) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:78) > Caused by: java.sql.SQLException: Cannot add or update a child row: a foreign key constraint fails > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2851) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1531) > at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1366) > at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:952) > at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1974) > at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1897) > at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1758) > at org.hibernate.jdbc.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:22) > at org.hibernate.persister.entity.BasicEntityPersister.insert(BasicEntityPersister.java:1853) > ... 17 more > Exception in thread "main" org.hibernate.exception.ConstraintViolationException: could not insert: [data.Foo] > at org.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:74) > at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) > at org.hibernate.persister.entity.BasicEntityPersister.insert(BasicEntityPersister.java:1869) > at org.hibernate.persister.entity.BasicEntityPersister.insert(BasicEntityPersister.java:2200) > at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:46) > at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:239) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:223) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:136) > at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:274) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:730) > at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:329) > at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:86) > at Test.reconstitute(Test.java:69) > at Test.main(Test.java:40) > And finally, here is the XML document I am attempting to reconstitute: > <root> > <Foo id="402881e4045ce90c01045ce90f950002"> > <prop1>abcd</prop1> > <bar>402881e4045ce90c01045ce90f770001</bar> > <index>0</index> > </Foo> > <Foo id="402881e4045ce90c01045ce90f9f0003"> > <prop1>456</prop1> > <bar>402881e4045ce90c01045ce90f770001</bar> > <index>1</index> > </Foo> > <Bar id="402881e4045ce90c01045ce90f770001"> > <foos> > <foo>402881e4045ce90c01045ce90f950002</foo> > <foo>402881e4045ce90c01045ce90f9f0003</foo> > </foos> > </Bar> > </root> -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:27
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718?page=all ] Steve Ebersole updated HHH-1718: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > Have multiple bag fetches revert to subselect fetching for all but one of the bags > ---------------------------------------------------------------------------------- > > Key: HHH-1718 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718 > Project: Hibernate3 > Type: Improvement > Components: query-hql, query-criteria, core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.0 > > > Follow on to HHH-1413. Multiple bag fetches were simply disallowed as the resolution to that particular case in the interest of working around that issue. > The correct longer term solution is to not fetch all the bags at once, ideally reverting to subselect fetching for all but one of the bags. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:26
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499?page=all ] Steve Ebersole updated HHH-1499: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows > --------------------------------------------------------------------------------------- > > Key: HHH-1499 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499 > Project: Hibernate3 > Type: Improvement > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.0 > > > As a follow on to HHH-1411and HHH-1412... > Both of those above were actually resolved by handling the DISTINCT-ion and/or firstResult/maxRows *in memory*. A better solution is to not honor the join fetch in these cases, perform the requested operation, and then get the requested join fectehd collections through subselect fetches. > As is, this would work as long as the collections have subselect fetching enabled in metadata, but would actually use immediate fetching (n+1) for any collections not defining subselect fetching in metadata. This is due to the way PersistenceContext.initializeNonLazyCollections() currently works. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:26
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-294?page=all ] Steve Ebersole updated HHH-294: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > implicit join in both subselect and outer query : single join > ------------------------------------------------------------- > > Key: HHH-294 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-294 > Project: Hibernate3 > Type: Improvement > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0 > > > See HHH-280 for the details. > Basically, that was fixed by reverting to the old parser output of generating duplicate joins. This should be fixed to use the same join both times for effeciency. > There were a number of ways we might acheive this: > 1) Somehow suspend processing of subqueries until their containing query is completely processed. The trick here is that the join definition from the outer query would already have been resolved when processing the inner query resumes at which point we could simply reuse the join def from the outer query (this is the same thing as putting the implicit join in the outer query *before* the subquery, which works). This approach (while simple in its concept) seems very difficult to acheive with the ANTLR parser. > 2) Perform some post processing sort of like we do with the "join post processing". Yuck! > 3) When attempting to resolve the DotNode (representing the implicit join) take a peek at "child from clauses" to see if any of them defined the same "implicit join path"; if so "promote" that join fragment from the child FromClause to the current FromClause. > I will attempt #3. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:26
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-434?page=all ] Steve Ebersole updated HHH-434: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > element/@attribute not implemented for collection elements > ---------------------------------------------------------- > > Key: HHH-434 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-434 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.3 > Reporter: Gavin King > Fix For: 3.2.0 > > > None of the following: > <element> > <one-to-many> > <many-to-many> > support use of node="element/@attribute", which is *extremely* useful when embed-xml="false" (the common case). > This is because we do not go via property accessors in the PersistentXXXElementHolder classes. Instead, we have hardcoded element iteration in about 16 different methods. > We need to find some design where this can be made more flexible. > Perhaps just CollectionPersister.getElementName() + CollectionPersister.getElementValue()/CollectionPersister.getElementValue() is enough, since PropertyAccessor is certainly not an appropriate solution. > Any volunteers? -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:26
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1539?page=all ] Steve Ebersole updated HHH-1539: -------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > JDK 1.4 dependencies in ResultSetWrapper, SerializableBlob and SerializableClob > ------------------------------------------------------------------------------- > > Key: HHH-1539 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1539 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.0 > Attachments: Hibernate3.1.2 Compilation Errors.xls > > > All these classes are simple wrappers. > We should write a proxy or AOPize that to not depend on JDK 1.4 APIs. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-796?page=all ] Steve Ebersole updated HHH-796: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > Hibernate fails to determine identifier of association inside composite-element in EntityMode.DOM4J when declared with embed-xml="false" > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-796 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-796 > Project: Hibernate3 > Type: Bug > Versions: 3.0.5 > Environment: Hibernate 3.0.5; Windows; MySQL 4.1 > Reporter: Vladimir Demochko > Fix For: 3.2.0 > Attachments: TestBug.zip > > > Having the following mapping declaration: > <class name="Parent"> > <id name="id"/> > <property name="label"/> > <bag name="associations" table="ASSOCIATION" cascade="all"> > <key column="PARENT_ID"/> > <composite-element class="Association" node="associations"> > <parent name="parent"/> > <many-to-one name="child" class="Child" column="CHILD_ID" node="child" embed-xml="false"/> > <property name="info" column="INFO" type="string"/> > </composite-element> > </bag> > </class> > <class name="Child"> > <id name="id"/> > <property name="info"/> > </class> > Hibernate fails with NullPointerException while constructing Parent/assosiations/child element (in fact while getting an identifier of a Child object) in EntityMode.DOM4J: > java.lang.NullPointerException > at org.hibernate.type.EntityType.getIdentifierType(EntityType.java:227) > at org.hibernate.type.EntityType.setToXMLNode(EntityType.java:417) > at org.hibernate.property.Dom4jAccessor$ElementSetter.set(Dom4jAccessor.java:307) > at org.hibernate.tuple.AbstractComponentTuplizer.setPropertyValues(AbstractComponentTuplizer.java:80) > at org.hibernate.type.ComponentType.setPropertyValues(ComponentType.java:262) > at org.hibernate.type.ComponentType.resolve(ComponentType.java:446) > at org.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:182) > at org.hibernate.persister.collection.AbstractCollectionPersister.readElement(AbstractCollectionPersister.java:612) > at org.hibernate.collection.PersistentElementHolder.readFrom(PersistentElementHolder.java:97) > at org.hibernate.loader.Loader.readCollectionElement(Loader.java:645) > at org.hibernate.loader.Loader.readCollectionElements(Loader.java:355) > at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:306) > at org.hibernate.loader.Loader.doQuery(Loader.java:395) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:210) > at org.hibernate.loader.Loader.loadCollection(Loader.java:1401) > at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:107) > at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:483) > at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) > at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1422) > at org.hibernate.type.CollectionType.getCollection(CollectionType.java:474) > at org.hibernate.type.CollectionType.resolveKey(CollectionType.java:332) > at org.hibernate.type.CollectionType.resolve(CollectionType.java:326) > at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:105) > at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:510) > at org.hibernate.loader.Loader.doQuery(Loader.java:419) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:210) > at org.hibernate.loader.Loader.loadEntity(Loader.java:1312) > at org.hibernate.loader.entity.EntityLoader.load(EntityLoader.java:116) > at org.hibernate.loader.entity.EntityLoader.load(EntityLoader.java:101) > at org.hibernate.persister.entity.BasicEntityPersister.load(BasicEntityPersister.java:2461) > at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:350) > at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:331) > at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:113) > at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:151) > at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:79) > at org.hibernate.impl.SessionImpl.get(SessionImpl.java:617) > at org.hibernate.impl.SessionImpl.get(SessionImpl.java:610) > at TestBug.main(TestBug.java:21) -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-05-06 04:36:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-874?page=all ] Steve Ebersole updated HHH-874: ------------------------------- Fix Version: 3.2.0 (was: 3.2.0.cr2) > org.hibernate.AssertionFailure: null owner only with EntityMode.DOM4J > --------------------------------------------------------------------- > > Key: HHH-874 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-874 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 beta 2 > Environment: Hibernate up to 3.1 beta 2, SQL Server > Reporter: Martin Caslavsky > Fix For: 3.2.0 > > > ERROR - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) > org.hibernate.AssertionFailure: null owner > at org.hibernate.collection.PersistentElementHolder.<init>(PersistentElementHolder.java:61) > at org.hibernate.type.SetType.instantiate(SetType.java:23) > at org.hibernate.engine.CollectionLoadContext.getLoadingCollection(CollectionLoadContext.java:101) > at org.hibernate.loader.Loader.readCollectionElement(Loader.java:990) > at org.hibernate.loader.Loader.readCollectionElements(Loader.java:635) > at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:579) > at org.hibernate.loader.Loader.doQuery(Loader.java:689) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223) > at org.hibernate.loader.Loader.loadCollection(Loader.java:1916) > at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:36) > at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520) > at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) > at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1555) > at org.hibernate.type.CollectionType.getCollection(CollectionType.java:501) > at org.hibernate.type.CollectionType.resolveKey(CollectionType.java:335) > at org.hibernate.type.CollectionType.resolve(CollectionType.java:329) > at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:113) > at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:842) > at org.hibernate.loader.Loader.doQuery(Loader.java:717) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223) > at org.hibernate.loader.Loader.loadEntity(Loader.java:1782) > at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:47) > at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:41) > at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2705) > at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:365) > at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:346) > at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123) > at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:177) > at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) > at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:774) > at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:746) > at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) > at org.hibernate.type.EntityType.resolve(EntityType.java:303) > at org.hibernate.type.EntityType.nullSafeGet(EntityType.java:217) > at org.hibernate.impl.IteratorImpl.postNext(IteratorImpl.java:93) > at org.hibernate.impl.IteratorImpl.next(IteratorImpl.java:120) > at ProduktCon.result(ProduktCon.java:42) > at AbstractCon.go(AbstractCon.java:114) > at Datacon.main(Datacon.java:31) > ProduktCon.java: > protected void result() { > Session session4 = factory.openSession().getSession(EntityMode.DOM4J); > Query query = session4.createQuery("select p from Produkt as p"); > for (Iterator it = query.iterate(); it.hasNext();) { > Element e = (Element) it.next(); // LINE 42 > } > } > Produkt.hbm.xml: > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping> > <class name="Produkt" table="eshop_prod" node="product"> > <id name="produkt" type="string" unsaved-value="any" column="produkt" node="@id"/> > <property name="cislo" column="Katalogove_cislo" node="@cislo"/> > <property name="popis" column="popis" node="name"/> > <property name="poznamka" column="poznamka" node="anotace"/> > <property name="text" column="text" node="descr"/> > <property name="zaruka" column="zaruka" node="@zaruka"/> > <property name="vyrobce" column="vyrobce" node="vyrobce"/> > <property name="dodavatel" column="dodavatel" node="dodavatel"/> > <property name="zarazeni" column="zarazeni" node="@zarazeni" /> > <property name="dostupnost" column="Carovy_kod_vlastni" node="@dostupnost" /> > <set name="kategorie" embed-xml="true" node="."> > <key column="produkt"/> > <one-to-many class="Kategorie"/> > </set> > <set name="related" embed-xml="true" node="." where="typ_souvislosti=0"> > <key column="produkt"/> > <one-to-many class="Related"/> > </set> > <set name="item" embed-xml="true" node="."> > <key column="vyrobek"/> > <one-to-many class="Item"/> > </set> > <set name="variant" embed-xml="true" node="."> > <key column="prod_id"/> > <one-to-many class="Variant"/> > </set> > </class> > </hibernate-mapping> > Last executed SQL statement: > Hibernate: select variant0_.prod_id as prod5_1_, variant0_.produkt as produkt1_, variant0_.produkt as produkt4_0_, variant0_.Katalogove_cislo as Katalogove2_4_0_, variant0_.Udaj_1 as Udaj3_4_0_, variant0_.Udaj_2 as Udaj4_4_0_ from data0001.dbo.eshop_variant variant0_ where variant0_.prod_id=? > This error occurs only with EntityMode.DOM4J. > Also when removed <set name="variant" ... > everything works OK. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
93 messages has been excluded from this view by a project administrator.
