August 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-610) Copy/paste errors in reference docs

by Christian Bauer (JIRA)

Copy/paste errors in reference docs ----------------------------------- Key: ANN-610 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-610 Project: Hibernate Annotations Issue Type: Bug Components: documentation Reporter: Christian Bauer Priority: Minor The section on bidirectional indexed collections has copy/paste errors. Also, show a List example and drop the map-key example. -- 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

16 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2457) UnsupportedOperationException with WebSphereExtendedJTATransactionLookup

by Erik Post (JIRA)

UnsupportedOperationException with WebSphereExtendedJTATransactionLookup ------------------------------------------------------------------------ Key: HHH-2457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457 Project: Hibernate3 Type: Bug Versions: 3.2.2 Reporter: Erik Post Using the WebSphereExtendedJTATransactionLookup as transaction manager lookup class results in an UnsupportedOperationException being thrown by WebSphereExtendedJTATransactionLookup$TransactionManagerAdapter.getStatus(). This method is called by JTATransactionFactory.isTransactionInProgress(). Would a solution be to have the TransactionManagerAdapter#getStatus method delegate to the TransactionAdapter#getStatus method? Also see http://forum.hibernate.org/viewtopic.php?t=966463 -- 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

16 years, 10 months

11
13
0 / 0

[Hibernate-JIRA] Created: (HHH-2073) many-to-one join fetch with optional parent causing stray query to fire

by Adam Hardy (JIRA)

many-to-one join fetch with optional parent causing stray query to fire ----------------------------------------------------------------------- Key: HHH-2073 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2073 Project: Hibernate3 Type: Bug Reporter: Adam Hardy Priority: Minor Attachments: bugtest.zip I have a call centre application which uses a mature database and is therefore pushing Hibernate to accomplish the mappings I need. The issue here is extra queries that Hibernate is firing where I set up the mapping to do a join in one hit. I am fetching child objects which may or may not have a parent. The child's foreign key points to a non-primary key on the parent. This is not reflected by a foreign key constraint in the database (hence it allows child to have no parent). If the child object has the foreign key 0 instead of null, which is the protocol in this database, then the parent which doesn't exist is not (& cannot) be instantiated, no problem, but then after processing the resultset, Hibernate fires off another query to fetch the parent that it could not find data for in the first query. This is obviously unnecessary in this context and degrades the performance on large searches on this child. I have classified it as minor since I suspect there may be work-arounds but I have not researched that yet. I didn't know whether I could put the mapping XML in the query, so I have attached a simplistic testcase example that demonstrates the problem. The following forum messages are relevant and the latter contains the mappings, which is easier than extracting them out of the testcase zip: http://forum.hibernate.org/viewtopic.php?t=960522 http://forum.hibernate.org/viewtopic.php?t=964211 -- 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

16 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2664) full join not working

by Fabio Tudone (JIRA)

full join not working --------------------- Key: HHH-2664 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2664 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4, 3.1.2 Environment: Any DB, tested on Windows Reporter: Fabio Tudone Attachments: test.jar I get this error when trying to full join: - 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: undefined join type 23 at org.hibernate.hql.ast.util.JoinProcessor.toHibernateJoinType(JoinProcessor.java:68) at org.hibernate.hql.ast.HqlSqlWalker.setImpliedJoinType(HqlSqlWalker.java:433) at org.hibernate.hql.antlr.HqlSqlBaseWalker.joinElement(HqlSqlBaseWalker.java:3157) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3067) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:2945) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:688) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:544) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) at com.finantix.test.Main.main(Main.java:63) -- 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

16 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-653) Exception when unidirection OneToMany relation defined in Embeded class

by Jifeng Liu (JIRA)

Exception when unidirection OneToMany relation defined in Embeded class ----------------------------------------------------------------------- Key: ANN-653 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-653 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate Core 3.2.5.ga Hibernate Annotations 3.3.0 GA Hibernate EntityManager 3.3.1 GA Reporter: Jifeng Liu Attachments: src.zip I got the following exception when I run the test case in attach file. It seems Hibernate throws Exception when unidirection OneToMany relation defined in Embeded class. Exception in thread "main" org.hibernate.AnnotationException: Illegal attempt to define a @JoinColumn with a mappedBy as sociation: htmlText.images at org.hibernate.cfg.Ejb3JoinColumn.buildJoinColumn(Ejb3JoinColumn.java:152) at org.hibernate.cfg.Ejb3JoinColumn.buildJoinColumns(Ejb3JoinColumn.java:127) at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1178) at org.hibernate.cfg.AnnotationBinder.fillComponent(AnnotationBinder.java:1731) at org.hibernate.cfg.AnnotationBinder.bindComponent(AnnotationBinder.java:1665) at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1544) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:733) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:498) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:277) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1269) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:150) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:888) at org.hibernate.ejb.Ejb3Configuration.createEntityManagerFactory(Ejb3Configuration.java:706) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:137) at test.Test.run(Test.java:24) at test.Test.main(Test.java:20) -- 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

16 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-295) mapping-file orm.xml not included

by Georges-Etienne Legendre (JIRA)

mapping-file orm.xml not included --------------------------------- Key: EJB-295 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-295 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Environment: Hibernate Core 3.2.4.GA Hibernate EntityManager 3.3.1.GA Reporter: Georges-Etienne Legendre We have the following situation: A jar library for our entity classes has been created. In it, there are these two files in the META-INF directory: persistence.xml and orm.xml. We define some common queries in the orm.xml file. This library is then used in another project. Because we would like to define other more specialized named queries in this project, we assumed that another orm.xml file (in the META-INF directoty) could be used. Without any workaround, it doesn't work. The entity manager only find/use the orm.xml contained in the library. To make it works, we have to add these 2 lines in the persistence.xml : <mapping-file>/META-INF/orm.xml</mapping-file> <mapping-file>/META-INF/orm.xml</mapping-file> The entity manager then includes both orm.xml files. In JSR 220, chapter 6.2.1.6, it's said: "... A object/relational mapping XML file named orm.xml may be specified in the META-INF directory in the root of the persistence unit or in the META-INF directory of any jar file referenced by the persistence. xml. Alternatively, or in addition, other mapping files may be referenced by the mapping-file elements of the persistence-unit element, and may be present anywhere on the class path." -- 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

16 years, 10 months

2
13
0 / 0

[Hibernate-JIRA] Created: (ANN-650) Explicitly disallow @Version on @Embedded and throw meaningful Exception

by Chris Bredesen (JIRA)

Explicitly disallow @Version on @Embedded and throw meaningful Exception ------------------------------------------------------------------------ Key: ANN-650 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-650 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate Annotations 3.3.0.GA Hibernate 3.2.2 Hibernate EntityManager 3.3.1.GA Reporter: Chris Bredesen Priority: Minor The above situation should be explicitly checked for and a meaningful exception thrown. Currently, this configuration blows up with the following trace: java.lang.ArrayIndexOutOfBoundsException: -66 at org.hibernate.persister.entity.AbstractEntityPersister.checkVersion(AbstractEntityPersister.java:1855) at org.hibernate.persister.entity.AbstractEntityPersister.generateUpdateString(AbstractEntityPersister.java:1811) at org.hibernate.persister.entity.AbstractEntityPersister.generateUpdateString(AbstractEntityPersister.java:1777) at org.hibernate.persister.entity.AbstractEntityPersister.postConstruct(AbstractEntityPersister.java:2930) at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:409) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:730) -- 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

16 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-591) SchemaExport throws ConcurrentModificationException for entity containing list of lists

by Ivan O'Connor (JIRA)

SchemaExport throws ConcurrentModificationException for entity containing list of lists --------------------------------------------------------------------------------------- Key: ANN-591 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-591 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.1 Environment: Hibernate 3.2.1.GA, Oracle 10 Reporter: Ivan O'Connor Attachments: hbm2ddl.zip I have a class, let's call it A, that contains a List of class B. Each instance of B has a List of class C. I'm trying to generate the DDL for this, so I've annotated the code and run it through SchemaExport, which throws a ConcurrentModificationException. My environment: Java 1.5, Oracle 10, Hibernate 3.2.1ga. The problem seems to be caused by having an entity (A) containing an embedded collection (of B), each element of which contains a collection (of C). SchemaExport generates correct DDL when the annotations are modified to make B and/or C an entity, but not when they are both components. I realise this is considered something of an exotic case, but I'd like to know why the DDL doesn't generate. See bugReport.txt in attached zip for further details. -- 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

16 years, 10 months

6
12
0 / 0

[Hibernate-JIRA] Created: (ANN-590) Table name problem

by Eddie Man (JIRA)

Table name problem ------------------ Key: ANN-590 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-590 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.1 Reporter: Eddie Man Priority: Critical Attachments: src.zip Problem: When I run the test.Main in the attachment, an mapping exception thrown while passing the annotation: Exception in thread "main" org.hibernate.MappingException: Unable to find column with logical name: customerID in ShoppingBasket at org.hibernate.cfg.Ejb3JoinColumn.checkReferencedColumnsType(Ejb3JoinColumn.java:383) at org.hibernate.cfg.BinderHelper.createSyntheticPropertyReference(BinderHelper.java:88) at org.hibernate.cfg.FkSecondPass.doSecondPass(FkSecondPass.java:63) at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:428) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:286) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) at test.Main.main(Main.java:19) But when I change the table name of ShoppingBaskets to "Basket", then the problem solved. -- 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

16 years, 10 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2728) Calling session.clear() while retrieving objects via an iterator will cause a "LazyInitializationException - No Session" by the CGLIBLazyInitializer

by Metin Göktay (JIRA)

Calling session.clear() while retrieving objects via an iterator will cause a "LazyInitializationException - No Session" by the CGLIBLazyInitializer ---------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2728 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2728 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Any Reporter: Metin Göktay Priority: Minor Given the following code Iterator stagingIterator = query.iterate("from "+entityName+" where importSourceFile.id = ?", deliveryId); // large result set while (stagingIterator.hasNext()) { Importable staging = stagingIterator.next(); Approvable approvable = this.approve(staging); tmp.add(approvable); i++; if (i % 200 == 0) { LOG.debug("Flushing+Clearing after "+i+" entries."); session.flush(); session.clear(); } } After clearing the session for the first time (resp. after the first 200 entries) the CGLIBInitializer object of next returned HibernateProxy object does not have a session any longer resulting in a "LazyInitializationException - No Session" exception. -- 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

16 years, 10 months

6
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2007