April 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-603) Using @CollectionOfEelements with FetchMode.JOIN and FetchType.EAGER to map a Map breaks Example criteria

by Philippe Laflamme (JIRA)

Using @CollectionOfEelements with FetchMode.JOIN and FetchType.EAGER to map a Map breaks Example criteria --------------------------------------------------------------------------------------------------------- Key: ANN-603 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-603 Project: Hibernate Annotations Issue Type: Bug Components: search Affects Versions: 3.3.0.ga Environment: hibernate-core-3.2.2.jar Reporter: Philippe Laflamme Attachments: ann-example_eager_join.patch I'm using CollectionOfElements to map a Map<String, @Embeddable>. I want it to eagerly join the associated table to fill the map. When I load the Entity using its PK, I obtain a single object with multiple entries in the Map, which is the expected behaviour. If I load the same Entity using an Example criteria (matching one of its property), I get one Entity per entry in the Map. If you use FetchMode.SELECT, the resulting Example query returns a single entity with multiple values in the Map (expected behaviour). Attached is a patch against annotations_3_3_0_GA that creates a test case in CollectionElementTest that reproduces the problem. -- 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

17 years, 5 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2066) HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table)

by XOrangOutan (JIRA)

HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table) ----------------------------------------------------------------------------------------------------------- Key: HHH-2066 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2066 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Environment: HSQL DB 1.8.x Reporter: XOrangOutan When trying to save an object that has an "incremental" primary key, Hibernate API tries to know what the max current id is by executing a "SELECT MAX". Though, in this particular sql query, schema name is not taken into account (in hsqldialect). This cause an error that prevents anyone from carrying out unit tests. This bug also exists on 3.x versions -- 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

17 years, 5 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2281) CLONE -Calling Session.connection() generates java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader

by Sergey Polzunov (JIRA)

CLONE -Calling Session.connection() generates java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2281 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2281 Project: Hibernate3 Type: Bug Versions: 3.2.1 Environment: Hibernate checked out from trunk; revision 10717 Reporter: Sergey Polzunov Calling Session.connection() always generates an exception. Here is the stacktrace I get from the attached test case: Exception in thread "main" java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581) at org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnectionProxy.java:56) at org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.java:163) at org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111) at org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359) at TestSession.main(TestSession.java:16) Changing the Connection.class.getClassLoader() to BorrowedConnectionProxy.class.getClassLoader() on line 57 in the generateProxy() method solves the problem. I am not very familiar with class loaders so I don't know if this is likeley to cause other problems elsewhere. Removing the ConnectionWrapper.class from the PROXY_INTERFACES array in the org.hibernate.jdbc.BorrowedConnectionProxy also solves the problem, but I guess it was added for a reason. -- 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

17 years, 5 months

11
17
0 / 0

[Hibernate-JIRA] Created: (HHH-2254) A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]"

by Hernan Liendo (JIRA)

A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-2254 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2254 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.0.ga Environment: Hibernate 3.2 using Sybase. However this is not an environment caused problem. It's supposed to happen in every environment. Reporter: Hernan Liendo -- Short description ============================================================================ -- A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]. Both Parent and Child use composite keys. -- Context ====================================================================================== -- Having composite keys for a Parent class and a Child class, I want to retrieve childs that belong to an specific Parent. -- Parent Definition ============================================================================ -- public class Parent { public ParentId ParentId; ... } public class ParentId { private String idField1; private int idField2; ... } // the parent mapping <hibernate-mapping> <class mutable="false" table="xx" name="Parent"> <composite-id class="ParentId" access="field" name="parentId"> <key-property column="idField1" access="field" name="idField1"/> <key-property column="idField2" access="field" name="idField2"/> </composite-id> </class> </hibernate-mapping> -- Child Definition ============================================================================ -- public class Child { public ChildId childId; ... } public class ChildId { public Parent parent; public String aditionalIdField; ... } // the mapping <hibernate-mapping> <class mutable="false" table="yyy" name="Child"> <composite-id class="ChildId" access="field" name="childId"> <key-many-to-one name="parent" class="Parent" access="field"> <column name="idField1" not-null="true" /> <column name="idField2" not-null="true" /> </key-many-to-one> <key-property column="aditionalIdField" access="field" name="aditionalIdField"/> </composite-id> </class> </hibernate-mapping> -- HQL Statement ============================================================================ -- from Child this where this.childId.parent = ? or from Child this where this.id.parent = ? // using aliased id -- The Exception ============================================================================ -- org.hibernate.QueryException: Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.childId.parent = ?] at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:319) at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:275) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:75) ... -- The Problem ============================================================================ -- class: org.hibernate.impl.AbstractQueryImpl method: protected void verifyParameters(boolean reserveFirstParameter) throws HibernateException line: 286 The method validates parameters. It resolves the "positionalValueSpan" variable witch in my case gets the value of 2 (One for parent's idField1 and the other for parent's idField2). The method compares positionalValueSpan (2) with parameterMetadata.getOrdinalParameterCount() witch it is 1 (the quantity of "?" signs in the HQL statement". This bug only happens when: 1. composed keys are used (and) 2. having a parent-child relationship (and) 3. resolving children from certain parent. -- Hibernate user workaround ============================================================================ -- Not to use a parent instance variable in the Child class. Hope this helps. If you guys need the source code in order to check the bug, please let me know it. Good luck! Hernan -- 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

17 years, 6 months

4
6
0 / 0

[Hibernate-JIRA] Created: (EJB-279) Entity Listener defined in orm.xml does not work

by Gary Ip (JIRA)

Entity Listener defined in orm.xml does not work ------------------------------------------------ Key: EJB-279 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-279 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.3.0.ga Environment: Hibernate core 3.2.2.GA, Hibernate Annotations 3.3.0.GA, Hibernate Entity Manager 3.3.0.GA, Spring 2.0.3, Tomcat 5.5.20, Oracle 9i Reporter: Gary Ip A default Entity Listener defined in orm.xml (this EJB3 deployment descriptor) worked in HEM and HAN 3.2.1 but not 3.3.0 http://forums.hibernate.org/viewtopic.php?t=972352&sid=95588b2c2391806158... -- 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

17 years, 6 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2592) force hibernate to generate use offset qeury when offset is zero

by Amir Pashazadeh (JIRA)

force hibernate to generate use offset qeury when offset is zero ---------------------------------------------------------------- Key: HHH-2592 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2592 Project: Hibernate3 Issue Type: Improvement Components: query-criteria, query-hql, query-sql Affects Versions: 3.2.3 Environment: Hibernate Core 3.2.3 + Hibernate Annotations 3.3.0 JDK 5.0 Oracle 10g r2 Reporter: Amir Pashazadeh Attachments: patch.zip I know this is mostly an Oracle issue, but believe me it is harder to fix it in Oracle! when the offset of a paged query is zero, Hibernate does not append offset part to query, but the result which is returned by oracle without the offset part, and result returned when offset is zero is different. so some records are retrieved in different pages, and some records (which must be in first page) are not retrieved at all. ---- the patch is included. (I've only included Oracle9Dialect which I used) -- 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

17 years, 7 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2586) Hibernate Serializable classes do not declare serialVersionUID

by Manuel Dominguez Sarmiento (JIRA)

Hibernate Serializable classes do not declare serialVersionUID -------------------------------------------------------------- Key: HHH-2586 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2586 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3, 3.2.2, 3.2.1, 3.2.0.ga, 3.2.0.cr5, 3.2.0.cr4, 3.2.0.cr3, 3.2.0.cr2, 3.2.0 cr1, 3.1.3, 3.2.0.alpha2, 3.2.0.alpha1, 3.1.2, 3.1.1, 3.1, 3.1 rc3, 3.1 rc2, 3.1 rc 1, 3.1 beta 2, 3.1 beta 1, 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0 final, 3.0 rc 1, 3.0 beta 4, 3.0 beta 3, 3.0 beta 2, 3.0 beta 1, 3.0 alpha Environment: Not specific to any database, platform or Hibernate version. Reporter: Manuel Dominguez Sarmiento None of the Serializable classes in Hibernate declare serialVersionUID (see http://www.hibernate.org/hib_docs/v3/api/serialized-form.html#org.hiberna...). This is recommended practice for ALL classes that implement the Serializable interface (see Joshua Bloch's Effective Java - Item #54). Adding these fields is trivial and takes little effort, but is a great enhancement if you are serializing Hibernate classes. For instance, we upgraded from Hibernate 3.2.2 to 3.2.3 in our production servers. We serialize process state (which sometimes includes references to Hibernate-managed entities) every 30 seconds or so and on shutdown, so in the event of failures or re-deployment, the processes can continue where they left off. We had a huge surprise when deserialization failed completely because AbstractPersistentCollection had slightly changed between the 3.2.2 and 3.2.3 releases, and this caused the automatically-generated default serialVersionUID to change, even though the changes in the serialized form are compatible as far as we can tell. -- 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

17 years, 7 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HBX-729) boolean types mapped to bit in MySQL 5 not working with EJB3 in JBoss 4.0.4.GA

by Daniel Pocock (JIRA)

boolean types mapped to bit in MySQL 5 not working with EJB3 in JBoss 4.0.4.GA ------------------------------------------------------------------------------ Key: HBX-729 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-729 Project: Hibernate Tools Type: Bug Versions: 3.2beta6 Environment: Debian Reporter: Daniel Pocock I define a property with type="boolean" in my .hbm.xml The generated SQL column defaults to bit(1). However, when using JBoss 4.0.4.GA and MySQL 5.0.22, reading the property (getXXX()) always return false If I force hbm2sql to generate a tinyint column, the boolean works as I would have expected: <column name="myColumn" sql-type="tinyint"/> -- 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

17 years, 7 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2477) lazy fetching ManyToOne produces inproper proxies when using single table inheritance strategy

by Daniel Nguyen (JIRA)

lazy fetching ManyToOne produces inproper proxies when using single table inheritance strategy ---------------------------------------------------------------------------------------------- Key: HHH-2477 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2477 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: hibernate 3.2.1-GA, postgresql 8.1 Reporter: Daniel Nguyen Attachments: bug.zip I have entity base class Vehicle and entity class Car which extends Vehicle (using single table inheritance strategy). I also have entity class User which have single-ended @ManyToOne relation from User to Vehicle with lazy fetching. Now there is a Car instance "c" and User instance "u" with relation to "c". Lazily fetching vehicle from "u" results with proxy object "o" which is instanceof Vehicle but not instanceof Car as expected. So it's impossible cast "o" to Car or at least read any of Car's property from "o". This is serious problem when inheritance is extensively used because inproper proxy object remains in cache. To walkaround I'd have to resign with lazy fetching (much performance loss) or manually replace proxy object in cache. testing code: SessionFactory sf = null; Session s = null; Transaction tx = null; try { sf = cfg.buildSessionFactory(); s = sf.openSession(); tx = s.beginTransaction(); //create car Car car = new Car(); car.setIdVehicle(1); car.setAge(5); s.save(car); //create user of car User user = new User(); user.setIdUser(1); user.setVehicle(car); s.save(user); //make sure it is actually added s.flush(); // test 1 - works ok, because we loaded vehicle before user s.clear(); //clear cache Vehicle vv = (Vehicle)s.get(Vehicle.class, 1); User uu = (User)s.get(User.class, 1); //we know that user vehicle is actually a Car Car cc = (Car)uu.getVehicle(); // test 2 - fails, when using lazy fetching s.clear(); //clear cache User u = (User)s.get(User.class, 1); Vehicle v = u.getVehicle(); //we know that user vehicle is actually a Car //so we cast to Car but ClassCastException is raised!!! Car c = (Car)v; //let's check what's actual class of v System.out.println(v.getClass().getName()); System.out.println(v.getClass().getSuperclass().getName()); //result: // test.hibernate.Vehicle$$EnhancerByCGLIB$$12ce1883 // test.hibernate.Vehicle //but I expected: // test.hibernate.Car$$EnhancerByCGLIB$$xxxxx // test.hibernate.Car } finally { if (tx!=null) tx.rollback(); if (s!=null) s.close(); if (sf!=null) sf.close(); } -- 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

17 years, 7 months

7
10
0 / 0

[Hibernate-JIRA] Created: (HBX-930) hbm2ddl: no outpufile on update="true"

by Nick Folder (JIRA)

hbm2ddl: no outpufile on update="true" -------------------------------------- Key: HBX-930 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-930 Project: Hibernate Tools Issue Type: Bug Components: ant Affects Versions: 3.2beta9 Environment: Hibernat 3.2, Oracle9i Reporter: Nick Folder Priority: Minor No outputfile is generated when option update is set to true. Example: <hbm2ddl export="false" outputfilename="sql.ddl" update="true" /> Thanks B -- 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

17 years, 7 months

4
3
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 April 2007