January 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3078) Problem with multiple classloaders and cglib proxy enhancement, e.g. in the usual tomcat configuration

by Pietu Pohjalainen (JIRA)

Problem with multiple classloaders and cglib proxy enhancement, e.g. in the usual tomcat configuration ------------------------------------------------------------------------------------------------------ Key: HHH-3078 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3078 Project: Hibernate3 Issue Type: Bug Components: build Affects Versions: 3.2.5, 3.1.3 Environment: Verified against Hibernate 3.1.3 and Hibernate 3.2.5ga. Reporter: Pietu Pohjalainen Attachments: hibernate-3.2.patch, LoadOrderTest.tar.gz In an usual tomcat classloader configuration, with hibernate3.jar residing in the Tomcat's common class loader and webapplications staying in their own classloaders, the cglib's proxy enhancement fails sometimes, as it tries to load the web application's classes via the Tomcat's common class loader. The main culprit is the interaction between Hibernate's PojoEntityTuplizer and cglib's AbstractClassGenerator. PojoEntityTuplizer passes a Set of interfaces to cglib for proxy enhancement. The set is constructed in method buildProxyFactory(PersistentClass, Getter, Setter). Now, depending on the interface classes hash codes, the order of included interfaces varies: sometimes Hibernate's HibernateProxy.class is the first one, sometimes it is the enhanced interface's class. Problems rise when the Set's iterator gives the interfaces in order of {HibernateProxy.class, InterfaceToBeEnhanced.class}. When performing the enhancing, the cglib chooses the first interface class's classloader to find all the other classes as well. Because HibernateProxy.class was loaded by Tomcat's common class loader, it cannot find the application's class InterfaceToBeEnhanced. Thus a ClassDefNotFoundError is thrown. There's a JUnit test demonstrating the case. Because the hashCodes of loaded classes is quite undeterministic (read: beyond my skills to make deterministic), I've included ten interface classes that should be cglib-enhanced. Most often, one of these enhancements fails, due to this bug. A fix would be to change hibernate to prioritize the application's interface classes over Hibernate's HibernateProxy.class in the set. This could be implemented by using LinkedHashSet instead of HashSet, and adding the HibernateProxy.class as the last one. This change does not introduce any faults to existing unit test sets, but allows the attaches JUnit test to run without failures. The attached patch is for Hibernate 3.2.5ga. -- 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, 11 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3707) Generate wrong CRUD SQL for joined-subclasses of union-subclass

by David Wang (JIRA)

Generate wrong CRUD SQL for joined-subclasses of union-subclass --------------------------------------------------------------- Key: HHH-3707 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3707 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate V3.2.6, Oracle 11g Reporter: David Wang Attachments: src.zip We use extension table to customerize our base line. Create one joined-subclass to the existed union-subclass in the project. For simple, I create simple sample to demo the error. UnionTableOne and UnionTableTwo are union-subclass of UnionTable. UnionTableOneExt is joined-subclass of UnionTableOne. See the attached files. Here list the hebernate mapping file. <hibernate-mapping package="union"> <class name="UnionTable" entity-name="UnionTable" abstract="true"> <id name="unionId" type="java.lang.Integer"> <column name="UNION_ID" /> <generator class="assigned" /> </id> </class> <union-subclass name="UnionTableOne" extends="UnionTable" entity-name="UnionTableOne" table="uniontableone"> <property name="oneName" column="ONE_NAME"></property> </union-subclass> <union-subclass name="UnionTableTwo" extends="UnionTable" entity-name="UnionTableTwo" table="uniontabletwo"> <property name="twoName" column="TWO_NAME"></property> </union-subclass> <joined-subclass name="UnionTableOneExt" extends="UnionTableOne" entity-name="UnionTableOneExt" table="uniontableone_ext"> <key column="UNION_ID"></key> <property name="extName" column="EXT_NAME"></property> </joined-subclass> </hibernate-mapping> When I create one UnionTableOneExt object, the generated SQL is insert into uniontableone_ext (ONE_NAME, EXT_NAME, UNION_ID) values (?, ?, ?); -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3702) dynamic HQLs definition similar to iBatis dynamic SQLs

by Amir Pashazadeh (JIRA)

dynamic HQLs definition similar to iBatis dynamic SQLs ------------------------------------------------------ Key: HHH-3702 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3702 Project: Hibernate Core Issue Type: New Feature Components: query-hql Affects Versions: 3.3.1 Reporter: Amir Pashazadeh it is a need to have some method to define dynamic HQLs like the way we can define dynamic SQLs in iBatis XMLs. there could be an annotation similar solution too. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3700) add support for DB2 feature OPTIMIZE FOR xx ROWS in SELECT

by Simon Jongsma (JIRA)

add support for DB2 feature OPTIMIZE FOR xx ROWS in SELECT ---------------------------------------------------------- Key: HHH-3700 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3700 Project: Hibernate Core Issue Type: Improvement Components: core Environment: DB2 UDB for ISeries 5.4 Reporter: Simon Jongsma It would be nice to have support for the (new) DB2 feature OPTIMIZE FOR xx ROWS. This clause can be added at the end of a SELECT statement. Hibernate could use the setMaxResults() value for xx (if it was provided). Hooks for this type of functionality could be implemented in the Dialect class. Example: public String addOptimizationClause(int maxResults, String select) { return select; } I tried to use the transformSelectString method that is in the Dialect class to add the suffix myself, but this did not work. transformSelectString is not consitently called (see HHH-3307). -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1570) criteria-api: filtering by key-many-to-one causes invalid sql

by Sanchit Srivastava (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1570?page=c... ] Sanchit Srivastava commented on HHH-1570: ----------------------------------------- I am using 3.2.6.ga version of hibernate and am still finding this issue... So i am unable to move along the association using a key-many-to-one association from table A to B (A contains composite key pointing to B and C tables) I tried using both criteria.createAlias and criteria.createCriteria ..... Using createAlias, as pointed out earlier, is creeating a wrong query (where clause b.property=? is created but the table B is missing from 'from clause' ). However createCriteria is not even creating the where clause... Do we have a fix for this on way or the Hibernate team is still working ... I find that the issue is still open, with no fix version specified.. so I assume this true.... Please can you provide a statuc on this? Regards & Thanks > criteria-api: filtering by key-many-to-one causes invalid sql > ------------------------------------------------------------- > > Key: HHH-1570 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1570 > Project: Hibernate Core > Issue Type: Bug > Components: query-criteria > Affects Versions: 3.1.2 > Reporter: Joris Verschoor > Attachments: hibernate.patch > > > We have a class Price that has a composite-id using a couple of key-properties and some key-many-to-ones) > One of those is "transportation", which has a many-to-one to transportationType > When we query using: criteria.add(Expression.eq("price.transportation.transportationType.id", transId);, we get an invalid SQL statement: The table of transportation was not selected. > I will try to make a testcase today or tomorrow, depending on my schedule.. Things will be more clear by then... > We have created a work-around, by mapping the transportationID twice: once in key-property, and once as a many-to-one. (instead of one key-many-to-one) -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3698) Problem with HQL parameter bindings as indexed collection selectors

by Steve Ebersole (JIRA)

Problem with HQL parameter bindings as indexed collection selectors ------------------------------------------------------------------- Key: HHH-3698 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3698 Project: Hibernate Core Issue Type: Bug Components: query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Minor Fix For: 3.2.x, 3.3.x, 3.4 Syntax like: from Zoo zoo where zoo.mammals[:name] = :id The portion inside the index operator (the brackets) is called the selector. If the selector is a parameter, there is a bug with the new parameter bind handling which misses them. Essentially this is/was a problem anywhere we were "pre rendering' the sql and injecting that into the actual AST tree as the generic SQL_TOKEN type. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3699) Problem with HQL parameter bindings for parameters in WITH join clause

by Steve Ebersole (JIRA)

Problem with HQL parameter bindings for parameters in WITH join clause ---------------------------------------------------------------------- Key: HHH-3699 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3699 Project: Hibernate Core Issue Type: Bug Components: query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Minor Fix For: 3.2.x, 3.3.x, 3.4 Essentially this is/was a problem anywhere we were "pre rendering' the sql and injecting that into the actual AST tree as the generic SQL_TOKEN type. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3671) The revision type field is not persisted when setting a custom revision type field name throught the properties

by Adam Warski (JIRA)

The revision type field is not persisted when setting a custom revision type field name throught the properties --------------------------------------------------------------------------------------------------------------- Key: HHH-3671 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3671 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Adam Warski Assignee: Adam Warski Fix For: 3.4 http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197239#4197239 -- 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, 11 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HV-43) Hibernate Validator could load JPA annotations for validation

by Leonardo Pinho (JIRA)

Hibernate Validator could load JPA annotations for validation ------------------------------------------------------------- Key: HV-43 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-43 Project: Hibernate Validator Issue Type: Improvement Affects Versions: 3.0.0.ga, 3.0.1 Reporter: Leonardo Pinho Priority: Critical Hibernate Validator could load JPA annotations fields for validation, like at @Column (javax.persistence.Column): public class Test { @Column(name="NAME", length=40, nullable=false) private String name; } Otherwise I have to change the code to: public class Test { @NotNull @Length(max=40) @Column(name="NAME", length=40, nullable=false) private String name; } And I got a redundant code... :( -- 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, 11 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3693) Implicit Polymorphic query + pagination returning zero result

by Anthony Patricio (JIRA)

Implicit Polymorphic query + pagination returning zero result ------------------------------------------------------------- Key: HHH-3693 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3693 Project: Hibernate Core Issue Type: Bug Components: query-criteria, query-hql Reporter: Anthony Patricio Running an implicit polymorphic query with pagination returns an empty list. simple example Query query = session.createQuery("from java.lang.Object"); query.setMaxResults(100); List results = query.list(); returned list will be empty -- 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, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2009