June 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3123) NullPointerException on invalid HQL query with an extra brace

by Geoffrey De Smet (JIRA)

NullPointerException on invalid HQL query with an extra brace ------------------------------------------------------------- Key: HHH-3123 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3123 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Reporter: Geoffrey De Smet Priority: Trivial This query: "select p from IndividueleRekeningKasPO p left join fetch p.irTotalen inner join fetch p.toegangIndividueleRekeningKas tirkas where tirkas.authorityRef in (:authorityref)) and p.soort = :soort and p.id > 0" gives a NPE. The strange thing is that this query executes: "select p from IndividueleRekeningKasPO p left join fetch p.irTotalen inner join fetch p.toegangIndividueleRekeningKas tirkas where tirkas.authorityRef in (:authorityref)) and p.id > 0" both are invalid, because there is a closing brace to much in "(:authorityref))". -- 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

15 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work

by Rohini (JIRA)

@TableGenerator throws Unsupported exception - error performing isolated work ----------------------------------------------------------------------------- Key: HHH-5019 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6, 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2, 3.2.1 Environment: Hibernate Core 3.3.1, MySQL, Websphere 6.1 with EJB3.0 Feature pack Reporter: Rohini While implementing GenerationType.TABLE strategy with Hibernate as the persistence provider, id generation throws javax.persistence.PersistenceException: org.hibernate.HibernateException: error performing isolated work [3/18/10 14:40:41:533 IST] 0000002d SystemErr R at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614) -------------------------------------------------------------- 3/18/10 14:40:41:533 IST] 0000002d SystemErr R Caused by: org.hibernate.HibernateException: error performing isolated work at org.hibernate.engine.transaction.Isolater$JtaDelegate.delegateWork(Isolater.java:166) at org.hibernate.engine.transaction.Isolater.doIsolatedWork(Isolater.java:64) at org.hibernate.engine.TransactionHelper.doWorkInNewTransaction(TransactionHelper.java:74) at org.hibernate.id.MultipleHiLoPerTableGenerator.generate(MultipleHiLoPerTableGenerator.java:210) Looking at the Isolater.doIsolatedWork( work, session );, implementation try { // First we need to suspend any current JTA transaction and obtain // a JDBC connection surroundingTransaction = transactionManager.suspend(); if ( log.isDebugEnabled() ) { log.debug( "surrounding JTA transaction suspended [" + surroundingTransaction + "]" ); } This happnes only with WebsphereExtendedTransactionManagerLookup as the hibernate.transaction.manager_lookup_class. -- 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

15 years, 2 months

6
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3934) Problem with PDF doc

by Adam Warski (JIRA)

Problem with PDF doc -------------------- Key: HHH-3934 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3934 Project: Hibernate Core Issue Type: Improvement Components: envers Reporter: Adam Warski Priority: Minor there is a problem on p.8 of the PDF documentation, the table is all jumbled + overlapping itself. -- 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

15 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5057) ScrollableResults does not fetch many-to-many collections

by Jérôme Van Der Linden (JIRA)

ScrollableResults does not fetch many-to-many collections --------------------------------------------------------- Key: HHH-5057 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5057 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Jérôme Van Der Linden Priority: Blocker I have a many-to-many relation between two objects : {code:title=Project.java|borderStyle=solid} @Entity public class Project { private List<Viperson> managers; @ManyToMany(targetEntity = Viperson.class) @JoinTable(name = "PRJMANAGER", joinColumns = @JoinColumn(name = "PROJECTID", nullable = false), inverseJoinColumns = @JoinColumn(name = "VIPID", nullable = false)) public List<Viperson> getManagers() { return managers; } } {code} {code:title=Viperson.java|borderStyle=solid} @Entity public class Viperson { private List<Project> projects; @ManyToMany(mappedBy = "managers", targetEntity = Project.class) public List<Project> getProjects() { return projects; } } {code} And the following test (actually, it is a code from spring batch HibernateCursorItemReader I put in a testcase) : {code} @Test public void testSelectAll() { StatelessSession statelessSession = sessionFactory.openStatelessSession(); ScrollableResults cursor = statelessSession.createQuery("from Project").scroll(); Object[] data = null; if (cursor.next()) { data = cursor.get(); } } {code} data contains a {{Project}} but {{managers}} field is *null*, +even if I add eager fetching+. I have also a {{OneToMany}} in the {{Project}} class. This one is well loaded (i have a {{PersistentBag}}). Is there anything I miss ? I suspect a bug on that. -- 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

15 years, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-843) Version increment not triggered on @OneToOne property modification having inverse owner

by Guenther Demetz (JIRA)

Version increment not triggered on @OneToOne property modification having inverse owner --------------------------------------------------------------------------------------- Key: ANN-843 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-843 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate 3.3.1.GA , Microsoft SQL Server Reporter: Guenther Demetz Priority: Minor Attachments: Testcase.jar In the revised "Java Persistence with Hibernate" book by Christian Bauer and Gavin King on page 464 there's written following about versioning: "If you use Hibernate as JPA provider ... every value-typed property modification .. triggers a version increment." Now I saw that Version increment indeed is not triggered on @OneToOne properties having an inverse owner (= mappedBy setted). This allows several concurrent transactions to set the association from same object towards different targets without having a OptimistickLockException at commit. This violates the ToOne policy! (Hibernate detects the inconsistency later when loading the property from database: org.hibernate.HibernateException: More than one row with the given identifier was found) Please see attached junit-testcase for reproducing the problem. regards Guenther Demetz -- 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

15 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4617) Using blobs with hibernate causes error

by Radosław Smogura (JIRA)

Using blobs with hibernate causes error --------------------------------------- Key: HHH-4617 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4617 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2 Environment: Hibernate 3.5-b2, Glassfish v3 promoted build 74, PostgreSQL 8.3.7 Reporter: Radosław Smogura Priority: Critical I have entity with byte[] property annotated as @Lob and lazy fetch type, when table is createad the created column is of type oid, but when the column is read in application, the Hibernate reads the OID value instead of bytes under given oid. It's behavior like to read / write bytea. If i remember well, auto-creating table with Hibernate creates oid column. The proper behavior for dealing in PostgreSQL (and this behavior is in Hibernate 3.4) is to use oids. -- 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

15 years, 2 months

4
16
0 / 0

[Hibernate-JIRA] Created: (HHH-5163) ClassCastException when Hibernate tries to cache results using ResultTransformer

by Strong Liu (JIRA)

ClassCastException when Hibernate tries to cache results using ResultTransformer -------------------------------------------------------------------------------- Key: HHH-5163 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5163 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Reporter: Strong Liu Assignee: Gail Badner Fix For: 3.5.x, 3.6 When Hibernate executes a cacheable query using a ResultTransformer, it will attempt to cache the results AFTER applying the ResultTransformer. The problem is that the ResultTransformer may modify the data in a way that Hibernate won't understand it anymore, and in this case it will generate a ClassCastException when trying to cache it. --------------------------- this can be reproduced by CriteriaQueryTest with following change: papa-pc:testsuite stliu$ svn diff src/test/java/org/hibernate/test/criteria/CriteriaQueryTest.java Index: src/test/java/org/hibernate/test/criteria/CriteriaQueryTest.java =================================================================== --- src/test/java/org/hibernate/test/criteria/CriteriaQueryTest.java (revision 19246) +++ src/test/java/org/hibernate/test/criteria/CriteriaQueryTest.java (working copy) @@ -613,6 +613,7 @@ ) .addOrder( Order.desc("studentName") ) .setResultTransformer( Transformers.aliasToBean(StudentDTO.class) ) + .setCacheable( true ) .list(); assertEquals(2, resultWithAliasedBean.size()); -- 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

15 years, 2 months

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3872) Criteria on alias causes partial collection materialization

by Adrian Moos (JIRA)

Criteria on alias causes partial collection materialization ----------------------------------------------------------- Key: HHH-3872 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3872 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.3.0.CR1 Reporter: Adrian Moos I have a parent entity with a one-to-many assocation to a child entity: <hibernate-mapping package="ch.bedag.a11.ccinfo.business.entity" default-lazy="false"> <class name="Parent" table="PARENT"> <id name="id" type="long" column="ID" unsaved-value="null"> <generator class="sequence"> <param name="sequence">SEQ_T_PARENT</param> </generator> </id> <set name="children" cascade="all-delete-orphan" inverse="true"> <key column="PARENT_ID" foreign-key="CHILD_FK1"/> <one-to-many class="Child"/> </set> </class> <class name="Child" <id name="id" type="long" column="ID" unsaved-value="null"> <generator class="sequence"> <param name="sequence">SEQ_T_CHILD</param> </generator> </id> <property name="businessKey" column="BUSINESSKEY" not-null="true"/> </class> </hibernate-mapping> I then do: Criteria parentCriteria = aSession.createCriteria(Parent.class); parentCriteria.createAlias("children", "c", CriteriaSpecification.LEFT_JOIN); parentCriteria.setResultTransformer(CriteriaSpecification.DISTINCT_ROOT_ENTITY); parentCriteria.add(Restrictions.eq("c.businessKey", 123456789)); List parents = parentCriteria.list(); Expected behaviour: Since each parent in parents is a materialized entity, I'd expect its children set to contain all its children. Observed behaviour: It contains only children with matching business key. Is my expectation correct? -- 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

15 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4878) Add documentation about new "image" and "text" properties

by Gail Badner (JIRA)

Add documentation about new "image" and "text" properties --------------------------------------------------------- Key: HHH-4878 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4878 Project: Hibernate Core Issue Type: Improvement Components: documentation Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5 -- 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

15 years, 3 months

3
18
0 / 0

[Hibernate-JIRA] Created: (HHH-3230) getEntityName() throws org.hibernate.TransientObjectException: proxy was not associated with the session

by Howard M. Lewis Ship (JIRA)

getEntityName() throws org.hibernate.TransientObjectException: proxy was not associated with the session -------------------------------------------------------------------------------------------------------- Key: HHH-3230 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3230 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Mac OS X, JDK 1.5 Reporter: Howard M. Lewis Ship I'm retrieving an entity that contains a OneToMany relationship. The master entity is retrieved, within a transaction, via Session.get(Class,Serializable). @Entity public class MapUnitSurvey extends ActiveDO { @ManyToOne(fetch = FetchType.LAZY) private VegetationType vegetationType; } @Entity public class VegetationType extends AbstractEnum { } ActiveDO and AbstractEnum are abstract base classes with @MappedSuperclass. I retrieve the vegationType: VegetationType type = survey.getVegetationType(); Then I need the type's entity name String entityName = session.getEntityName(type); This fails with the TransientObjectException. Inspecting with the debugger, I see that type is a CGLIB-enhanced proxy, and that there's a fully initialized bean in the target field of the proxy. I'll attach a screenshot of some debugging data. In summary; the entity was retrieved via a lazy fetch, appears the be correct, seems to be in the session and yet the exception occurs. I've tried to resolve this by re-fetching the object from the session, and a few other tries, with no luck. -- 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

15 years, 3 months

4
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2010