September 2011 - hibernate-issues

[Hibernate-JIRA] Created: (HSEARCH-444) Search fails to start when core uses XML mappings making use of entity-name attribute

by Sanne Grinovero (JIRA)

Search fails to start when core uses XML mappings making use of entity-name attribute ------------------------------------------------------------------------------------- Key: HSEARCH-444 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-444 Project: Hibernate Search Issue Type: Bug Components: mapping Affects Versions: 3.1.0.GA Reporter: Sanne Grinovero Assignee: Emmanuel Bernard Fix For: 3.2.0.Beta2 As described on forums: https://forum.hibernate.org/viewtopic.php?f=9&t=993687 classes mapped using XML on hibernate core, like classes starting with: <class name="com.mydomain.myapp.AnswerImpl" table="answer" entity-name="Answer"> cause: Caused by: java.lang.NullPointerException at org.hibernate.search.cfg.SearchConfigurationFromHibernateCore.getClassMapping(SearchConfigurationFromHibernateCore.java:31) at org.hibernate.search.store.DirectoryProviderFactory.getDirectoryProviderName(DirectoryProviderFactory.java:226) at org.hibernate.search.store.DirectoryProviderFactory.createDirectoryProviders(DirectoryProviderFactory.java:53) at org.hibernate.search.impl.SearchFactoryImpl.initDocumentBuilders(SearchFactoryImpl.java:404) at org.hibernate.search.impl.SearchFactoryImpl.<init>(SearchFactoryImpl.java:119) at org.hibernate.search.event.ContextHolder.getOrBuildSearchFactory(ContextHolder.java:30) at org.hibernate.search.event.FullTextIndexEventListener.initialize(FullTextIndexEventListener.java:59) at org.hibernate.event.EventListeners$1.processListener(EventListeners.java:198) at org.hibernate.event.EventListeners.processListeners(EventListeners.java:181) at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:194) ... 16 more This was reported on 3.1.0.GA but I guess it affects all releases. There's a "test WAR" in the forums, going to ask for a testcase. -- 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

11 years, 12 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2058) puhs SessionImplementor.getInterceptor up into Session

by Max Rydahl Andersen (JIRA)

puhs SessionImplementor.getInterceptor up into Session ------------------------------------------------------ Key: HHH-2058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2058 Project: Hibernate3 Type: Improvement Components: core Reporter: Max Rydahl Andersen Being able to get the actual interceptor used for a certain Session is beneficial. any reason why it is not exposed on Session ? -- 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

11 years, 12 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-816) Make it possible to configure an alternative DeletionPolicy

by Sanne Grinovero (JIRA)

Make it possible to configure an alternative DeletionPolicy ----------------------------------------------------------- Key: HSEARCH-816 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-816 Project: Hibernate Search Issue Type: New Feature Reporter: Sanne Grinovero Priority: Minor Fix For: 4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3129) Null Role in PersitentCollection during a onCollectionRecreate() in an Interceptor

by Jose CHILLAN (JIRA)

Null Role in PersitentCollection during a onCollectionRecreate() in an Interceptor ---------------------------------------------------------------------------------- Key: HHH-3129 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3129 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Any Reporter: Jose CHILLAN When the "onCollectionRecreate" is invoked on an Interceptor, the getRole() method returns null. After investigation, the problem is located in the class CollectionEntry in one of its constructors and is easily solved using the patch : public CollectionEntry(CollectionPersister persister, PersistentCollection collection) { // new collections that get found + wrapped // during flush shouldn't be ignored ignore = false; collection.clearDirty(); //a newly wrapped collection is NOT dirty (or we get unnecessary version updates) snapshot = persister.isMutable() ? collection.getSnapshot(persister) : null; // -- ADDED LINE HERE -- role = persister.getRole(); collection.setSnapshot(loadedKey, role, snapshot); } Thanks -- 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

11 years, 12 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6491) Support @javax.persistence.SqlResultSetMapping(s) including @javax.persitence.EntityResult and @javax.persistence.ColumnResult

by Hardy Ferentschik (JIRA)

Support @javax.persistence.SqlResultSetMapping(s) including @javax.persitence.EntityResult and @javax.persistence.ColumnResult ------------------------------------------------------------------------------------------------------------------------------ Key: HHH-6491 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6491 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6492) Support @javax.persistence.Enumerated

by Strong Liu (JIRA)

Support @javax.persistence.Enumerated ------------------------------------- Key: HHH-6492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6492 Project: Hibernate Core Issue Type: Sub-task Components: metamodel Reporter: Strong Liu -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6580) Discriminator value used as ID when inserting entity to PosgtreSQL

by Paweł Stawicki (JIRA)

Discriminator value used as ID when inserting entity to PosgtreSQL ------------------------------------------------------------------ Key: HHH-6580 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6580 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.6, 3.6.5, 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6.0 Environment: Tested on Hibernate 3.6.0, but I looked in the code of 3.6.6 and 4.0.0 Beta4 and it looks like it isn't fixed. PostgreSQL 8.4.8 Reporter: Paweł Stawicki When we have inheritance strategy SINGLE_TABLE, and we use discriminator column, this column is the first one in table. Now we want to insert some entity inheriting from this one, and we want PostgreSQL to automatically generate the ID for the new entity. Discriminator column is the first in the table. Hibernate runs IdentityGenerator.GetGeneratedKeysDelegate.executeAndExtract(), which gets ResultSet from PreparedStatement (in Hibernate 3.6.0 it's line 97 in IdentityGenerator). This ResultSet, in case of PostgreSQL, contains whole inserted row, not only ID. This is the problem if ID is not the first column, because then Hibernate get's value from the first column and uses it as ID. It's in IdentifierGeneratorHelper.getGeneratedIdentity() and IdentifierGeneratorHelper.get(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
14
0 / 0

[Hibernate-JIRA] Created: (HHH-6391) Add EntityBinding.getJoinClosureSpan(), getJoinClosure(), getJoinNumber()

by Gail Badner (JIRA)

Add EntityBinding.getJoinClosureSpan(), getJoinClosure(), getJoinNumber() ------------------------------------------------------------------------- Key: HHH-6391 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6391 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Gail Badner Fix For: 4.0.0.next -- 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

12 years

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5733) PersistenceUnitUtil.getIdentifier returns null for lazy loaded relations.

by Jaroslaw Lewandowski (JIRA)

PersistenceUnitUtil.getIdentifier returns null for lazy loaded relations. ------------------------------------------------------------------------- Key: HHH-5733 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5733 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.0, 3.6.1 Reporter: Jaroslaw Lewandowski Attachments: IdentityTest.tgz Test unit attached. Basically when entity A references entity B which is lazy loaded then calling PersistenceUnitUtil.getIdentifier(A.getB()) might return null. -- 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

12 years

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2847) THIS_"."NAME": invalid identifier when using createCriteria with addOrder

by Ashish Tiwari (JIRA)

THIS_"."NAME": invalid identifier when using createCriteria with addOrder ------------------------------------------------------------------------- Key: HHH-2847 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2847 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.0.5 Environment: Oracle - 10.2.0 Reporter: Ashish Tiwari We are using hibernate 3.0.5 and once a while I see following error getting generated due to incorrect SQL generated by hibernate: Hibernate: select systembean0_.SYSTEMID as SYSTEMID12_0_, systembean0_.Version as Version12_0_, systembean0_.NAME as NAME12_0_, systembean0_.TYPE as TYPE12_0_, systembean0_.DESCRIPTION as DESCRIPT5_12_0_ from SDSYSTEM systembean0_ order by this_.NAME asc - SQL Error: 904, SQLState: 42000 - ORA-00904: "THIS_"."NAME": invalid identifier This normally works but occasionally we run into the issue mentioned above. I do not see alias "this_" in the sql query and I think that causes the error to happen. Issue is caused by alias not used consistently. In normal case the generated SQL looks like following: Hibernate: select this_.SYSTEMID as SYSTEMID7_0_, this_.Version as Version7_0_, this_.NAME as NAME7_0_, this_.TYPE as TYPE7_0_, this_.DESCRIPTION as DESCRIPT5_7_0_ from SDSYSTEM this_ order by this_.NAME asc I am not sure what causes this problem. Has anyone else see similar problem earlier? I appreciate any help with this. Below is other information: Hibernate version: 3.0.5 Mapping documents: <?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="com.avaya.coreservice.admin.toolkit.common.system.SystemBean" table="SDSYSTEM"> <id name="uniqueId" type="java.lang.String"> <column name="SYSTEMID" length="50" not-null="true"/> <generator class="uuid"/> </id> <version name="version" column="Version" /> <property name="name" type="java.lang.String"> <column name="NAME" length="512" not-null="true"/> </property> <property name="type" type="java.lang.String"> <column name="TYPE" length="50" not-null="false"/> </property> <property name="description" type="java.lang.String"> <column name="DESCRIPTION" length="1024" not-null="false"/> </property> <set name="resourceBeanSet"> <key> <column name="SYSTEMID" length="50" not-null="false"/> </key> <one-to-many class="com.avaya.coreservice.admin.toolkit.common.resource.ResourceBean"/> </set> <set name="siteBeanSet" order-by="name asc"> <key> <column name="SYSTEMID" length="50" not-null="false"/> </key> <one-to-many class="com.avaya.coreservice.admin.toolkit.common.site.SiteBean"/> </set> </class> </hibernate-mapping> Code between sessionFactory.openSession() and session.close(): HibernateUtil.getSession().createCriteria(SystemBean.class) .addOrder(Order.asc("name")).list(); Full stack trace of any exception that occurs: N/A Name and version of the database you are using: Oracle - 10.2.0 The generated SQL (show_sql=true): select systembean0_.SYSTEMID as SYSTEMID12_0_, systembean0_.Version as Version12_0_, systembean0_.NAME as NAME12_0_, systembean0_.TYPE as TYPE12_0_, systembean0_.DESCRIPTION as DESCRIPT5_12_0_ from SDSYSTEM systembean0_ order by this_.NAME asc I appreciate any help with this. Thanks, -- 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

12 years

7
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2011