August 2006 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-1740) Build-time instrumentation breaks lazy="proxy"

by Frank Grimes (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c... ] Frank Grimes commented on HHH-1740: ----------------------------------- I checked out the latest from SVN TRUNK and applied my changes as outlined in HHH-1740.diff but the problem is still present. Could this issue be re-opened until this is resolved? FYI, I had to apply the following changes just to get buildtime tests to run (There was a NullPointerException being thrown): ****************************************************************************************************************************** Index: D:/eclipse-3.1/workspaces/invex-stratix/Hibernate3/test/org/hibernate/test/instrument/buildtime/InstrumentTest.java =================================================================== --- D:/eclipse-3.1/workspaces/invex-stratix/Hibernate3/test/org/hibernate/test/instrument/buildtime/InstrumentTest.java (revision 10252) +++ D:/eclipse-3.1/workspaces/invex-stratix/Hibernate3/test/org/hibernate/test/instrument/buildtime/InstrumentTest.java (working copy) @@ -25,31 +25,52 @@ } public void testDirtyCheck() { - new TestDirtyCheckExecutable().execute(); + TestDirtyCheckExecutable exec = new TestDirtyCheckExecutable(); + exec.prepare(); + exec.execute(); + exec.complete(); } public void testFetchAll() throws Exception { - new TestFetchAllExecutable().execute(); + TestFetchAllExecutable exec = new TestFetchAllExecutable(); + exec.prepare(); + exec.execute(); + exec.complete(); } public void testLazy() throws Exception { - new TestLazyExecutable().execute(); + TestLazyExecutable exec = new TestLazyExecutable(); + exec.prepare(); + exec.execute(); + exec.complete(); } public void testLazyManyToOne() { - new TestLazyManyToOneExecutable().execute(); + TestLazyManyToOneExecutable exec = new TestLazyManyToOneExecutable(); + exec.prepare(); + exec.execute(); + exec.complete(); } public void testSetFieldInterceptor() { - new TestInjectFieldInterceptorExecutable().execute(); + TestInjectFieldInterceptorExecutable exec = new TestInjectFieldInterceptorExecutable(); + exec.prepare(); + exec.execute(); + exec.complete(); } public void testPropertyInitialized() { - new TestIsPropertyInitializedExecutable().execute(); + TestIsPropertyInitializedExecutable exec = new TestIsPropertyInitializedExecutable(); + exec.prepare(); + exec.execute(); + exec.complete(); } public void testManyToOneProxy() { - new TestManyToOneProxyExecutable().execute(); + TestManyToOneProxyExecutable exec = new TestManyToOneProxyExecutable(); + exec.prepare(); + exec.execute(); + exec.complete(); } protected String[] getMappings() { ****************************************************************************************************************************** Also, the runtime tests are all failing with the following errors: Caused an ERROR (class: org/hibernate/test/instrument/runtime/AbstractTransformingClassLoaderInstrumentTestCase$1, method: <init> signature: (Lorg/hibernate/test/instrument/runtime/AbstractTransformingClassLoaderInstrumentTestCase;)V) Expecting to find object/array on staP? java.lang.VerifyError: (class: org/hibernate/test/instrument/runtime/AbstractTransformingClassLoaderInstrumentTestCase$1, method: <init> signature: (Lorg/hibernate/test/instrument/runtime/AbstractTransformingClassLoaderInstrumentTestCase;)V) Expecting to find object/array on staP? at org.hibernate.test.instrument.runtime.AbstractTransformingClassLoaderInstrumentTestCase.buildIsolatedClassLoader(AbstractTransformingClassLoaderInstrumentTestCase.java:19) at org.hibernate.test.AbstractClassLoaderIsolatedTestCase.setUp(AbstractClassLoaderIsolatedTestCase.java:16) > Build-time instrumentation breaks lazy="proxy" > ---------------------------------------------- > > Key: HHH-1740 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2 > Reporter: Frank Grimes > Assignee: Steve Ebersole > Priority: Critical > Fix For: 3.2.0.ga > Attachments: 312Document.class, Document.class, HHH-1740.diff > > > I have a mapping that contains a many-to-one lazy="proxy". > This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load > Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks. > Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object) > This works fine in hibernate-3.1.2. > This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881 > Please let me know if more info or a test case is needed. -- 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, 10 months

1
0
0 / 0

Mail list migration complete

by Steve Ebersole

Migration of the Hibernate email lists to their new hosting home is now complete. As of today, automated emails have been fully cut over: JIRA -> hibernate-issues(a)lists.jboss.org SVN -> hibernate-commits(a)lists.jboss.org CruiseControl -> hibernate-dev(a)lists.jboss.org For the past 2 weeks or so I have been monitoring both of the dev lists. As of next week, that will stop and I will only continue to subscribe to hibernate-dev(a)lists.jboss.org The hibernate-announce(a)lists.jboss.org is new and we'll see how it goes. It is supposed to be used for general announcements, release notifications, etc. For example, I intend to send release announcements to both hibernate-announce(a)lists.jboss.org and hibernate-dev@lists.jboss.org... Thanks! Steve

17 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1355) Post update event listener semantics changed from Hibernate 3.0 to 3.1

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1355?page=all ] Steve Ebersole updated HHH-1355: -------------------------------- Priority: Major (was: Blocker) most definitely not a blocker > Post update event listener semantics changed from Hibernate 3.0 to 3.1 > ---------------------------------------------------------------------- > > Key: HHH-1355 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1355 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Reporter: Pekka Enberg > Assignee: Steve Ebersole > Fix For: 3.2.0.ga > > > We are using Hibernate event model to implement transparent localization of POJOs. It is implemented as PreUpdateEventListener and PostUpdateEventListener so that a POJO is manipulated at PreUpdateEventListener before letting Hibernate to persist it and restored in PostUpdateEventListener. This works in Hibernate 3.0 but in 3.1 post update event semantics have changed so now we are unable to restore the state without Hibernate thinking the POJO is dirty. > This issue is related to the following forum topic: http://forum.hibernate.org/viewtopic.php?t=953934 -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Assigned: (HHH-1355) Post update event listener semantics changed from Hibernate 3.0 to 3.1

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1355?page=all ] Steve Ebersole reassigned HHH-1355: ----------------------------------- Assign To: Steve Ebersole > Post update event listener semantics changed from Hibernate 3.0 to 3.1 > ---------------------------------------------------------------------- > > Key: HHH-1355 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1355 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Reporter: Pekka Enberg > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > We are using Hibernate event model to implement transparent localization of POJOs. It is implemented as PreUpdateEventListener and PostUpdateEventListener so that a POJO is manipulated at PreUpdateEventListener before letting Hibernate to persist it and restored in PostUpdateEventListener. This works in Hibernate 3.0 but in 3.1 post update event semantics have changed so now we are unable to restore the state without Hibernate thinking the POJO is dirty. > This issue is related to the following forum topic: http://forum.hibernate.org/viewtopic.php?t=953934 -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1355) Post update event listener semantics changed from Hibernate 3.0 to 3.1

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1355?page=c... ] Steve Ebersole commented on HHH-1355: ------------------------------------- That code block you refer to was added for dealing with generated properties which was a major feature added between 3.0 and 3.1. I need a *simplified* test case illustrating the issue you have. > Post update event listener semantics changed from Hibernate 3.0 to 3.1 > ---------------------------------------------------------------------- > > Key: HHH-1355 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1355 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1 > Reporter: Pekka Enberg > Priority: Blocker > Fix For: 3.2.0.ga > > > We are using Hibernate event model to implement transparent localization of POJOs. It is implemented as PreUpdateEventListener and PostUpdateEventListener so that a POJO is manipulated at PreUpdateEventListener before letting Hibernate to persist it and restored in PostUpdateEventListener. This works in Hibernate 3.0 but in 3.1 post update event semantics have changed so now we are unable to restore the state without Hibernate thinking the POJO is dirty. > This issue is related to the following forum topic: http://forum.hibernate.org/viewtopic.php?t=953934 -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1949) having trim(BOTH from c.name) translated into having ltrim(rtrim(BOTH)) on DB2

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1949?page=all ] Steve Ebersole resolved HHH-1949: --------------------------------- Resolution: Fixed fixed for db2 and friends much like we did for SQL Server via the use of an "emulation" function which combines ltrim(), rtrim(), and replace() to mimic ANSI trim() functionality. derby unfortunately does not even have a standard replace function; so there I cheated a little bit and simply said that specifying the replacement character is not supported... > having trim(BOTH from c.name) translated into having ltrim(rtrim(BOTH)) on DB2 > ------------------------------------------------------------------------------ > > Key: HHH-1949 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1949 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.2.0.cr3 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0.ga > > > same for LEADING and TRAILING -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1610) many-to-one objects and hibernate-mapping default-lazy="false"

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1610?page=all ] Steve Ebersole closed HHH-1610: ------------------------------- Resolution: Incomplete > many-to-one objects and hibernate-mapping default-lazy="false" > -------------------------------------------------------------- > > Key: HHH-1610 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1610 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3 > Environment: 3.1.3, MSSQL 2000, Tomcat 5.5.12, JRE 1.5.0_06-b05 > Reporter: Oleg Byelkin > > > After migration from hibernate 3.1.2 to 3.1.3 I figured out that all my <many-to-one ...> objects become lazy loading in runtime (I use build time instrumentation). > In other words, if you explicitly set default-lazy to "false" and lazy identificator for many-to-one was omitted, then you many-to-one class will be lazy-loaded in runtime. > My typical mapping file looks like below. If I try get access to branch.getCompany(), I'll get an exception org.hibernate.exception.GenericJDBCException: could not initialize lazy properties: [package.Company]. > ... > <hibernate-mapping default-lazy="false"> > <class name="package.Branch" table="branch"> > ... > <many-to-one name="company" class="package.Company" > not-null="true" access="field" outer-join="false"> > <column name="company" sql-type="char(32)"/> > </many-to-one> > ... > </class> > </hibernate-mapping> > --- -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1740) Build-time instrumentation breaks lazy="proxy"

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=all ] Steve Ebersole resolved HHH-1740: --------------------------------- Fix Version: 3.2.0.ga Resolution: Fixed applied to both trunk and 3.2 branch > Build-time instrumentation breaks lazy="proxy" > ---------------------------------------------- > > Key: HHH-1740 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2 > Reporter: Frank Grimes > Assignee: Steve Ebersole > Priority: Critical > Fix For: 3.2.0.ga > Attachments: 312Document.class, Document.class, HHH-1740.diff > > > I have a mapping that contains a many-to-one lazy="proxy". > This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load > Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks. > Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object) > This works fine in hibernate-3.1.2. > This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881 > Please let me know if more info or a test case is needed. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-1996) "ORDER BY ?" named parameter in named query ignored

by W. Muir (JIRA)

"ORDER BY ?" named parameter in named query ignored --------------------------------------------------- Key: HHH-1996 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1996 Project: Hibernate3 Type: Bug Components: query-sql, query-hql Versions: 3.1.3 Environment: hibernate 3.1.3, java 1.5.0_06-b05, mysql 5.0.21 Reporter: W. Muir a named query, that contains a named parameter in the "ORDER BY" clause is ignored/removed. example: <query name="test"> <![CDATA[ FROM SomeObject so WHERE 1=1 ORDER BY :order ]]> </query> case 1 : named parameter set Query query = session.getNamedQuery( "test" ); query.setString( "order ", "so.id" ); List list = query.list(); // results are not ordered by id (or what ever you set for the named paraemeter) case 2: named parameter NOT set Query query = session.getNamedQuery( "test" ); // query.setString( "order ", "so.id" ); List list = query.list(); Exception in thread "main" org.hibernate.QueryException: Not all named parameters have been set: [order] [ FROM SomeObject so WHERE 1=1 ORDER BY :order ] 1. Should some sort of exceptioin be thrown (NotSupportedException, or something)? 2. bump this to a feature request? Related? http://opensource.atlassian.com/projects/hibernate/browse/HB-297 -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Assigned: (HHH-1740) Build-time instrumentation breaks lazy="proxy"

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=all ] Steve Ebersole reassigned HHH-1740: ----------------------------------- Assign To: Steve Ebersole (was: Scott Marlow) > Build-time instrumentation breaks lazy="proxy" > ---------------------------------------------- > > Key: HHH-1740 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2 > Reporter: Frank Grimes > Assignee: Steve Ebersole > Priority: Critical > Attachments: 312Document.class, Document.class, HHH-1740.diff > > > I have a mapping that contains a many-to-one lazy="proxy". > This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load > Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks. > Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object) > This works fine in hibernate-3.1.2. > This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881 > Please let me know if more info or a test case is needed. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2006