Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: <leg...@at...> - 2003-10-15 17:29:20
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-403 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-403 Summary: hbm2java- Composite-element inherits "extends" meta attribute from class. Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Components: toolset Versions: 2.0.3 Assignee: Reporter: Jason Stiefel Created: Wed, 15 Oct 2003 12:28 PM Updated: Wed, 15 Oct 2003 12:28 PM Environment: JDK 1.4 Description: When using hbm2java a composite-element inherits the parent class "extends" meta attribute. For example, the class generated for the composite-element below will extend "LifecycleSupport" for some reason. :-) <hibernate-mapping> <class name="com.pwc.us.factiva.entity.Newsfeed" table="EXTRA_NEWSFEED"> <meta attribute="extends">com.pwc.us.factiva.entity.LifecycleSupport</meta> .... <list name="selectedMetadata" table="EXTRA_NEWSFEED_METADATA" cascade="none" lazy="true"> <key column="NEWSFEED_ID"/> <index column="INDEX"/> <composite-element class="com.pwc.us.factiva.entity.MetadataSelection"> <parent name="newsfeed"/> <property name="condition" type="com.pwc.us.factiva.entity.ConditionType" column="CONDITION_TYPE"/> <many-to-one name="metadata" column="METADATA_ID" class="com.pwc.us.factiva.entity.Metadata"/> </composite-element> </list> </class> </hibernate-mapping> --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-15 17:09:20
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Wed, 15 Oct 2003 12:08 PM
Comment:
This is not a bug.
Note that you should be able to work around this by using functional form "sysdate()"
Changes:
type changed from Bug
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-402&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-402
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-402
Summary: where clause in collection mapping ignores dialect keywords
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 beta 4
Assignee:
Reporter: Edina Pimp
Created: Wed, 15 Oct 2003 11:36 AM
Updated: Wed, 15 Oct 2003 12:08 PM
Environment: oracle, jdk1.3.1_08
Description:
When the optional where clause supplied in a collection mapping is parsed, dialect specific keywords are ignored, resulting in invalid SQL being generated.
<example code>
Template.renderWhereStringTemplate(
"x < sysdate",
new Oracle9Dialect());
produces:
$PlaceHolder.x < $PlaceHolder.sysdate
</example code>
Possible fix may be to add additional code to logic beginning on line 59 of Template that starts
boolean isIdentifier = ...
New logic would check the current dialect's function map, etc.
-dc
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 16:37:28
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-402 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-402 Summary: where clause in collection mapping ignores dialect keywords Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 beta 4 Assignee: Reporter: Edina Pimp Created: Wed, 15 Oct 2003 11:36 AM Updated: Wed, 15 Oct 2003 11:36 AM Environment: oracle, jdk1.3.1_08 Description: When the optional where clause supplied in a collection mapping is parsed, dialect specific keywords are ignored, resulting in invalid SQL being generated. <example code> Template.renderWhereStringTemplate( "x < sysdate", new Oracle9Dialect()); produces: $PlaceHolder.x < $PlaceHolder.sysdate </example code> Possible fix may be to add additional code to logic beginning on line 59 of Template that starts boolean isIdentifier = ... New logic would check the current dialect's function map, etc. -dc --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-15 15:18:11
|
The following comment has been added to this issue:
Author: David Morris
Created: Wed, 15 Oct 2003 10:12 AM
Body:
In some cases I have configurations that only have dynamically configured mappings using Config.addClass(Class). I find this works very well and is more flexible. I haven't tested to confirm, but I suspect this reduces startup overhead for small standalone applications.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-397
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-397
Summary: Hibernate configuration DTD should not require mapping(s)
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Tue, 14 Oct 2003 12:24 AM
Updated: Wed, 15 Oct 2003 6:54 AM
Description:
The hibernate-configuration dtd defines mapping as a 1-many relationship to mappings. This makes it impossible to use a session configuration without at least one mapping defined. I have attached a patch, however the change is trivial, just change mapping+ to mapping* in http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd (will this become 2.1?).
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 14:48:21
|
The following comment has been added to this issue:
Author: Dominik Roblek
Created: Wed, 15 Oct 2003 9:47 AM
Body:
Just one idea: Persistent class PersonEntity, which fails in 2.1beta4 has one speciality. It is mapped as joined subclass and it's parametereless constructor sets value of one of its property, which is mapped with Hibernate. Maybe bacause if this reason Hibernate (in fact CGLIB) in beta4 cannot create proxy factory.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-401
Summary: reflection optimizer bug
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee: Gavin King
Reporter: Dominik Roblek
Created: Wed, 15 Oct 2003 5:32 AM
Updated: Wed, 15 Oct 2003 6:56 AM
Description:
I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine:
---
14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory
14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null
14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null
14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory
---
But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here:
---
12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed
net.sf.cglib.CodeGenerationException
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181)
at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222)
at net.sf.cglib.Enhancer.enhance(Enhancer.java:149)
at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52)
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754)
at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737)
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660)
...
---
Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value.
Dominik
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 14:38:35
|
The following comment has been added to this issue:
Author: Dominik Roblek
Created: Wed, 15 Oct 2003 9:38 AM
Body:
We definitely did instantiate proxies for classes, which now cause failure.
For the concrete example we used:
session.load(PersonEntity.class, new Long(2334));
It worked perfectly fine.
Look at the attached PartyEntity.hbm.xml
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-401
Summary: reflection optimizer bug
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee: Gavin King
Reporter: Dominik Roblek
Created: Wed, 15 Oct 2003 5:32 AM
Updated: Wed, 15 Oct 2003 6:56 AM
Description:
I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine:
---
14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory
14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null
14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null
14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory
---
But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here:
---
12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed
net.sf.cglib.CodeGenerationException
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181)
at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222)
at net.sf.cglib.Enhancer.enhance(Enhancer.java:149)
at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52)
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754)
at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737)
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660)
...
---
Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value.
Dominik
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 13:03:20
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 15 Oct 2003 8:02 AM
Body:
I stronly suspect that the only difference is that it now fails "earlier". I bet that previously Hibernate did not actually instantiate any proxy. (eg. you only used find() to get instances of the class).
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-401
Summary: reflection optimizer bug
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee: Gavin King
Reporter: Dominik Roblek
Created: Wed, 15 Oct 2003 5:32 AM
Updated: Wed, 15 Oct 2003 6:56 AM
Description:
I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine:
---
14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory
14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null
14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null
14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory
---
But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here:
---
12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed
net.sf.cglib.CodeGenerationException
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181)
at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222)
at net.sf.cglib.Enhancer.enhance(Enhancer.java:149)
at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52)
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754)
at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737)
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660)
...
---
Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value.
Dominik
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 12:15:19
|
The following comment has been added to this issue:
Author: Dominik Roblek
Created: Wed, 15 Oct 2003 7:15 AM
Body:
I checked everything again. My class is mapped with a proxy and because of this reason fails in 2.1beta4. The same class with completely the same mapping works perfectly with Hibernate versions prior to 2.1beta4.
The same class mapped without proxy works in 2.1beta4.
Is this a bug or are there new conditions, under which class can be mapped with a proxy?
Dominik
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-401
Summary: reflection optimizer bug
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee: Gavin King
Reporter: Dominik Roblek
Created: Wed, 15 Oct 2003 5:32 AM
Updated: Wed, 15 Oct 2003 6:56 AM
Description:
I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine:
---
14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory
14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null
14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null
14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory
---
But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here:
---
12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed
net.sf.cglib.CodeGenerationException
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181)
at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222)
at net.sf.cglib.Enhancer.enhance(Enhancer.java:149)
at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52)
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754)
at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737)
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660)
...
---
Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value.
Dominik
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 12:11:20
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Wed, 15 Oct 2003 7:10 AM
Body:
...to be able to just use the xml configuration file to setup the basic stuff....and then add mapping files via code...
We have the same possibility with hbm.xml files - they can also be totally empty ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-397
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-397
Summary: Hibernate configuration DTD should not require mapping(s)
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Tue, 14 Oct 2003 12:24 AM
Updated: Wed, 15 Oct 2003 6:54 AM
Description:
The hibernate-configuration dtd defines mapping as a 1-many relationship to mappings. This makes it impossible to use a session configuration without at least one mapping defined. I have attached a patch, however the change is trivial, just change mapping+ to mapping* in http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd (will this become 2.1?).
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 12:05:20
|
Message: The following issue has been re-assigned. Assignee: Christian Bauer (mailto:chr...@hi...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-391 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-391 Summary: Udated bat files in the tools - defined HIBERNATE_HOME Type: Patch Status: Assigned Priority: Major Project: Hibernate2 Components: toolset Assignee: Christian Bauer Reporter: Mukund Pragasam Created: Fri, 10 Oct 2003 8:31 AM Updated: Mon, 13 Oct 2003 12:06 PM Environment: run the tools (like hbm2java) from any other IDE like JBuilder. Description: In the tools/bin we have class2hbm.bat ddl2hbm.bat hbm2java.bat setenv.bat all the above bat files need to know HIBERNATE_HOME they were using relative path to get it. When I run these tools from JBuilder, they were not working because of the relative path. I extracted hibernate-extensions-2.0.zip in the hibernate home directory. So I had the directory structure like avalon bin build.bat build.xml changelog.txt demo.bat demo.sh doc hibernate2.jar hibernate_logo.gif lgpl.txt lib readme.txt src tools I have modified the files to get HIBERNATE_HOME from the environment variables. For example if "%HIBERNATE_HOME%"=="" goto noHIBERNATEHome call %HIBERNATE_HOME%\tools\bin\setenv.bat java -cp %CP% net.sf.hibernate.tool.class2hbm.MapGenerator %* if not "%HIBERNATE_HOME%"=="" goto end :noHIBERNATEHome echo HIBERNATE_HOME is not set. Please set HIBERNATE_HOME. :end set HIBERNATE_HOME I can send this to the group and they can update this in their copy. I can send all the bat files with similar updates. I am not sure how this works. Will this be Assigned To me? or Do I need to send the modified bat files in a mail...? --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-15 12:00:20
|
The following comment has been added to this issue:
Author: Dominik Roblek
Created: Wed, 15 Oct 2003 6:59 AM
Body:
Sorry, my mistake. My classes uses proxy. Why proxy with this class cannot be used with 2.1beta4? It worked perfectly in 2.1beta3 and before.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-401
Summary: reflection optimizer bug
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee: Gavin King
Reporter: Dominik Roblek
Created: Wed, 15 Oct 2003 5:32 AM
Updated: Wed, 15 Oct 2003 6:56 AM
Description:
I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine:
---
14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory
14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null
14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null
14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory
---
But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here:
---
12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed
net.sf.cglib.CodeGenerationException
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181)
at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222)
at net.sf.cglib.Enhancer.enhance(Enhancer.java:149)
at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52)
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754)
at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737)
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660)
...
---
Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value.
Dominik
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 11:58:40
|
The following issue has been updated:
Updater: Dominik Roblek (mailto:dr...@ya...)
Date: Wed, 15 Oct 2003 6:56 AM
Comment:
My class is not mapped as a proxy. Completely same class with same mapping works perfectly with version 2.1beta3 and I susspect this is bug in beta4. Here is my mapping attached.
Changes:
Attachment changed to PartyEntity.hbm.xml
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-401
Summary: reflection optimizer bug
Type: Bug
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee: Gavin King
Reporter: Dominik Roblek
Created: Wed, 15 Oct 2003 5:32 AM
Updated: Wed, 15 Oct 2003 6:56 AM
Description:
I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine:
---
14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory
14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null
14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null
14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory
---
But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here:
---
12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed
net.sf.cglib.CodeGenerationException
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181)
at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222)
at net.sf.cglib.Enhancer.enhance(Enhancer.java:149)
at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52)
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754)
at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737)
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660)
...
---
Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value.
Dominik
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 11:54:20
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Wed, 15 Oct 2003 6:54 AM
Comment:
What exactly is the reason for a session factory with no mappings?? Seems a bit strange....
Changes:
type changed from Bug
priority changed from Major
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-397&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-397
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-397
Summary: Hibernate configuration DTD should not require mapping(s)
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Tue, 14 Oct 2003 12:24 AM
Updated: Wed, 15 Oct 2003 6:54 AM
Description:
The hibernate-configuration dtd defines mapping as a 1-many relationship to mappings. This makes it impossible to use a session configuration without at least one mapping defined. I have attached a patch, however the change is trivial, just change mapping+ to mapping* in http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd (will this become 2.1?).
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 11:52:21
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 15 Oct 2003 6:52 AM
fixed it
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-400
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-400
Summary: StrinBuffer.append(StringBuffer) breaks JDK 1.3 in HSQL Dialect
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 beta 5
Versions:
2.0.3
Assignee:
Reporter: Steve Kwee
Created: Tue, 14 Oct 2003 10:36 AM
Updated: Wed, 15 Oct 2003 6:52 AM
Description:
package net.sf.hibernate.sql
class HSQLCaseFragment
method toFragmentString
StrinBuffer.append(StringBuffer) is a JDK 1.4 feature and breaks
breaks JDK1.3.x compatibility
look for
buf.append(buf2);
should be
buf.append(buf2.toString());
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 11:48:22
|
Message: The following issue has been re-assigned. Assignee: Gavin King (mailto:ga...@in...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-401 Summary: reflection optimizer bug Type: Bug Status: Assigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 4 Assignee: Gavin King Reporter: Dominik Roblek Created: Wed, 15 Oct 2003 5:32 AM Updated: Wed, 15 Oct 2003 6:48 AM Description: I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine: --- 14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory 14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null 14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null 14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory --- But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here: --- 12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed net.sf.cglib.CodeGenerationException at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200) at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186) at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181) at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222) at net.sf.cglib.Enhancer.enhance(Enhancer.java:149) at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52) at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754) at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737) at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63) at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132) at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660) ... --- Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value. Dominik --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-15 11:48:22
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 15 Oct 2003 6:47 AM
Body:
This is nothing to do with the reflection optimizer. Hibernate is trying to create a -proxy- factory in this section of code. I strongly suspect that your class is mapped with a proxy, but cannot be proxied in any version of Hibernate.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-401
Summary: reflection optimizer bug
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: Dominik Roblek
Created: Wed, 15 Oct 2003 5:32 AM
Updated: Wed, 15 Oct 2003 5:32 AM
Description:
I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine:
---
14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory
14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null
14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null
14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory
---
But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here:
---
12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed
net.sf.cglib.CodeGenerationException
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186)
at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181)
at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222)
at net.sf.cglib.Enhancer.enhance(Enhancer.java:149)
at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52)
at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754)
at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737)
at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660)
...
---
Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value.
Dominik
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 11:44:19
|
Message: The following issue has been re-assigned. Assignee: Max Rydahl Andersen (mailto:xa...@xa...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-396 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-396 Summary: hbm2java validate method code generation Type: Patch Status: Assigned Priority: Minor Project: Hibernate2 Components: toolset Versions: 2.0 final Assignee: Max Rydahl Andersen Reporter: Rob Stokes Created: Mon, 13 Oct 2003 4:59 PM Updated: Wed, 15 Oct 2003 6:43 AM Environment: Hibernate Extensions 2.0 Description: This patch contains the code to generate the validate() method for classes that implement net.sf.hibernate.Validatable interface. The validate method will check nullablity and string lengths check based on the mapping file. As part of the nullability checks it also add static initializers for collection type variables. Any checks that fail will throw a ValidationFailure exception with a message loaded from a resource bundle created by ValidatableMessageRenderer. ValidatableMessageRenderer must be added to the config.xml used by hbm2java. The messages can then be modified to what ever you want them to say. --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-15 11:42:26
|
Message:
The following issue has been re-assigned.
Assignee: Gavin King (mailto:ga...@in...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Wed, 15 Oct 2003 6:41 AM
Comment:
agreed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-399
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-399
Summary: Query.setLockMode support for databases that do not support FOR UPDATE OF
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee: Gavin King
Reporter: Gerjon de Vries
Created: Tue, 14 Oct 2003 8:02 AM
Updated: Wed, 15 Oct 2003 6:41 AM
Environment: MySql 3.23.48-Max, using mysql-connector-java-3.0.8-stable
Description:
Query.setLockMode("alias", LockMode.UPGRADE) won't set a lockmode if the dialect does not support "FOR UPDATE OF" syntax. However, if the query is on only one table, or if all table aliases have a lockmode.upgrade, it could still set the lockmode by using "FOR UPDATE" instead of FOR UPDATE OF.
Also, instead of silently ignoring the lockmode if the dialect does not support FOR UPDATE OF, one could make a case case for using "FOR UPDATE" instead, for such dialects. This would assure the at least the specified locks are set, while the current behaviour is to just ignore the locks.
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-15 10:32:20
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-401 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-401 Summary: reflection optimizer bug Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 4 Assignee: Reporter: Dominik Roblek Created: Wed, 15 Oct 2003 5:32 AM Updated: Wed, 15 Oct 2003 5:32 AM Description: I have some persistent classes, which cannot be instrumented with CGLIB reflection optimizer. In Hibernate versions prior to 2.1beta4 I've got the following correct log messages and everything worked fine: --- 14:26:48,230 INFO [:] SessionFactoryImpl:109 - building session factory 14:26:57,507 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.PersonEntity, NullPointerException: null 14:26:59,175 INFO [:] ReflectHelper:328 - reflection optimizer disabled for: si.marand.maf.server.jastreb.party.module.entity.BankEntity, NullPointerException: null 14:27:06,349 INFO [:] SessionFactoryObjectFactory:86 - Factory name: maf-server-hibernate-sessionFactory --- But in version 2.1beta4 is instead of this in the same phase of startup process thrown an exception, which stops application. The excerption from log it here: --- 12:18:51,464 ERROR [:] LazyInitializer:62 - CGLIB Enhancement failed net.sf.cglib.CodeGenerationException at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:200) at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:186) at net.sf.cglib.ReflectUtils.newInstance(ReflectUtils.java:181) at net.sf.cglib.Enhancer.enhanceHelper(Enhancer.java:222) at net.sf.cglib.Enhancer.enhance(Enhancer.java:149) at net.sf.hibernate.proxy.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:52) at net.sf.hibernate.persister.AbstractEntityPersister.<init>(AbstractEntityPersister.java:754) at net.sf.hibernate.persister.NormalizedEntityPersister.<init>(NormalizedEntityPersister.java:737) at net.sf.hibernate.persister.PersisterFactory.create(PersisterFactory.java:63) at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:132) at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:660) ... --- Besides of this bug it seems, that hibernate.cglib.use_reflection_optimizer setting is ignored in beta4 and "true" is allways used as it's value. Dominik --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-14 15:37:21
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-400 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-400 Summary: StrinBuffer.append(StringBuffer) breaks JDK 1.3 in HSQL Dialect Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: Steve Kwee Created: Tue, 14 Oct 2003 10:36 AM Updated: Tue, 14 Oct 2003 10:36 AM Description: package net.sf.hibernate.sql class HSQLCaseFragment method toFragmentString StrinBuffer.append(StringBuffer) is a JDK 1.4 feature and breaks breaks JDK1.3.x compatibility look for buf.append(buf2); should be buf.append(buf2.toString()); --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-14 13:03:21
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-399 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-399 Summary: Query.setLockMode support for databases that do not support FOR UPDATE OF Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: Gerjon de Vries Created: Tue, 14 Oct 2003 8:02 AM Updated: Tue, 14 Oct 2003 8:02 AM Environment: MySql 3.23.48-Max, using mysql-connector-java-3.0.8-stable Description: Query.setLockMode("alias", LockMode.UPGRADE) won't set a lockmode if the dialect does not support "FOR UPDATE OF" syntax. However, if the query is on only one table, or if all table aliases have a lockmode.upgrade, it could still set the lockmode by using "FOR UPDATE" instead of FOR UPDATE OF. Also, instead of silently ignoring the lockmode if the dialect does not support FOR UPDATE OF, one could make a case case for using "FOR UPDATE" instead, for such dialects. This would assure the at least the specified locks are set, while the current behaviour is to just ignore the locks. --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-14 12:36:23
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-398 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-398 Summary: Support for LOCK IN SHARE MODE Type: New Feature Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: Gerjon de Vries Created: Tue, 14 Oct 2003 7:35 AM Updated: Tue, 14 Oct 2003 7:35 AM Environment: Not specific Description: Currently hibernate supports explicit locking strategies via LockMode.UPGRADE and LockMode.READ. However, there does not seem to be a lockmode that represents the SELECT xxxx LOCK IN SHARE MODE. (I.e. to select row(s) that should not be altered by other sessions, and need not be altered by the current transaction). Is this going to be supported? --------------------------------------------------------------------- JIRA INFORMATION: 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.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-14 11:01:37
|
The following comment has been added to this issue:
Author: Ralf Taugerbeck
Created: Tue, 14 Oct 2003 6:00 AM
Body:
Sorry, wrong path.
Index: WebSphereTransactionManagerLookup.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/transaction/WebSphereTransactionManagerLookup.java,v
retrieving revision 1.5.2.5
diff -u -r1.5.2.5 WebSphereTransactionManagerLookup.java
--- WebSphereTransactionManagerLookup.java 13 Oct 2003 09:08:16 -0000 1.5.2.5
+++ WebSphereTransactionManagerLookup.java 14 Oct 2003 10:40:25 -0000
@@ -17,7 +17,6 @@
public class WebSphereTransactionManagerLookup implements TransactionManagerLookup {
private static final Log log = LogFactory.getLog(WebSphereTransactionManagerLookup.class);
- private int version;
/**
* @see net.sf.hibernate.transaction.TransactionManagerLookup#getTransactionManager(Properties)
@@ -27,12 +26,10 @@
Class clazz;
try {
clazz = Class.forName("com.ibm.ejs.jts.jta.TransactionManagerFactory");
- version = 5;
log.info("WebSphere 5");
}
catch (Exception e) {
clazz = Class.forName("com.ibm.ejs.jts.jta.JTSXA");
- version = 4;
log.info("WebSphere 4");
}
@@ -44,9 +41,7 @@
}
public String getUserTransactionName() {
- return version==5 ?
- "java:comp/UserTransaction":
- "jta/usertransaction";
+ return "java:comp/UserTransaction";
}
}
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-365
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-365
Summary: TransactionManagerLookup for WebSphere 5.0
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 beta 4
Versions:
2.1
2.0.3
Assignee: Daniel Bradby
Reporter: Ralf Taugerbeck
Created: Fri, 26 Sep 2003 5:08 AM
Updated: Fri, 3 Oct 2003 5:08 AM
Environment: WebSphere 5.0
Description:
The TransactionManagerLookup issue on WebSphere 5.0 was already resolved in HB-240 but IMO the code should look as shown in the attached Patch.
BTW, there is no class "com.ibm.ejcs.jts.jta.JTSXA" in WAS 5.0
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-14 10:59:21
|
The following comment has been added to this issue:
Author: Ralf Taugerbeck
Created: Tue, 14 Oct 2003 5:58 AM
Body:
I took another look into the WebSphere 5.0 Documentation and found the following section (http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/cjta_glotran.html):
"Before the EJB 1.1 specification, the JNDI location of the UserTransaction interface was not specified. Each EJB container implementor defined it in an implementation-specific manner. Earlier versions of WebSphere Application Server, up to and including Version 3.5.x (without EJB 1.1), bind the UserTransaction interface to a JNDI location of jta/usertransaction. WebSphere Application Server Version 4, and later releases, bind the UserTransaction interface at the location defined by EJB 1.1, which is java:comp/UserTransaction. WebSphere Application Server, Version 5 no longer provides the jta/usertransaction binding within Web and EJB containers to applications at a J2EE level of 1.3 or later. For example, EJB 2.0 applications can use only the java:comp/UserTransaction location."
This would mean that <i>java:comp/UserTransaction</i> is the first choice for both WAS 4.0 and WAS 5.0. <i>jta/usertransaction</i> is just for backward compatibility.
I would suggest to further simplify the code and apply the patch:
Index: WebSphereTransactionManagerLookup.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/transaction/WebSphereTransactionManagerLookup.java,v
retrieving revision 1.5.2.5
diff -r1.5.2.5 WebSphereTransactionManagerLookup.java
20d19
< private int version;
30d28
< version = 5;
35d32
< version = 4;
47,49c44
< return version==5 ?
< "java:comp/UserTransaction":
< "jta/usertransaction";
---
> return "java:comp/UserTransaction";
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-365
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-365
Summary: TransactionManagerLookup for WebSphere 5.0
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 beta 4
Versions:
2.1
2.0.3
Assignee: Daniel Bradby
Reporter: Ralf Taugerbeck
Created: Fri, 26 Sep 2003 5:08 AM
Updated: Fri, 3 Oct 2003 5:08 AM
Environment: WebSphere 5.0
Description:
The TransactionManagerLookup issue on WebSphere 5.0 was already resolved in HB-240 but IMO the code should look as shown in the attached Patch.
BTW, there is no class "com.ibm.ejcs.jts.jta.JTSXA" in WAS 5.0
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-14 05:27:19
|
The following issue has been updated:
Updater: David Morris (mailto:dmm...@ce...)
Date: Tue, 14 Oct 2003 12:25 AM
Changes:
Attachment changed to dtdmapping.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-397&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-397
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-397
Summary: Hibernate configuration DTD should not require mapping(s)
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Tue, 14 Oct 2003 12:24 AM
Updated: Tue, 14 Oct 2003 12:25 AM
Description:
The hibernate-configuration dtd defines mapping as a 1-many relationship to mappings. This makes it impossible to use a session configuration without at least one mapping defined. I have attached a patch, however the change is trivial, just change mapping+ to mapping* in http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd (will this become 2.1?).
---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
93 messages has been excluded from this view by a project administrator.
