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-12-25 08:44:25
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-577 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-577 Summary: hibernate.show_sql improvement Type: Improvement Status: Closed Priority: Minor Resolution: REJECTED Project: Hibernate2 Versions: 2.1.1 Assignee: Reporter: Leonid Shlyapnikov Created: Wed, 24 Dec 2003 10:30 AM Updated: Thu, 25 Dec 2003 2:44 AM Environment: Linux version 2.4.21-144-smp4G (ro...@i3...) (gcc version 3.3.1 (SuSE Linux)) #1 SMP Fri Nov 14 00:07:01 UTC 2003; jdk 1.4.2; jboss-3.2.2; Description: It would be more useful if hibernate logged its SQL queries in more details. I mean symbols '?' in the logged query. The real values would help to determine problems. BTW, TopLink logs SQL queries fully :) A part of show_sql log: 18:42:14,506 INFO [STDOUT] Hibernate: insert into RequestInfo (DurationMeasurementId, FromDate, Duration, EnterDate, ModificationDate, ProlongationOpportunity, RequestInfoDescription, RequestId, RequestInfoID) values (?, ?, ?, ?, ?, ?, ?, ?, ?) bash: syntax error near unexpected token `(' shl@shl:~/javalib/hibernate-2.1/src> 18:42:14,506 INFO [STDOUT] Hibernate: insert into Demand (Commission, PriceFrom, PriceTo, RequestInfoId) values (?, ?, ?, ?) bash: syntax error near unexpected token `(' shl@shl:~/javalib/hibernate-2.1/src> 18:42:24,759 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 22P02 bash: 18:42:24,759: command not found shl@shl:~/javalib/hibernate-2.1/src> 18:42:24,759 ERROR [JDBCExceptionReporter] ERROR: invalid input syntax for integer: "\254\355\000\005sr\000!ru.incom.solaris.common.UniqueKey8\344\2432{\016\316T\002\000\001L\000\003keyt\000\020Ljava/lang/Long;xpsr\000\016java.lang.Long;\213\344\220\314\217#\337\002\000\001J\000\005valuexr\000\020java.lang.Number\206\254\225\035\013\224\340\213\002\000\000xp\000\000\000\000\000\000\000\002" --------------------------------------------------------------------- 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-12-25 00:31:26
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-578 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-578 Summary: Junit test case failed Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1.1 Assignee: Reporter: Vivek Venugopalan Created: Wed, 24 Dec 2003 6:31 PM Updated: Wed, 24 Dec 2003 6:31 PM Environment: MySQL 4.0.14b, JConnector 3.0 and new download of 2.1.1 version Description: I recently downloaded Hybernate 2.1.1 and tried to run the examples which ran fine. Then executed the junits to verify if things worked fine. The test Class org.hibernate.test.FooBarTest.testPersistCollections failed with the following error. could not deserialize net.sf.hibernate.type.SerializationException: could not deserialize at net.sf.hibernate.util.SerializationHelper.deserialize(SerializationHelper.java:194) at net.sf.hibernate.util.SerializationHelper.deserialize(SerializationHelper.java:220) at org.hibernate.test.FooBarTest.testPersistCollections(FooBarTest.java:2262) at org.hibernate.test.TestCase.runTest(TestCase.java:80) Caused by: java.lang.ClassNotFoundException: long at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:195) at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:654) at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1142) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:374) at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2263) at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1412) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236) at java.util.HashMap.readObject(HashMap.java:840) at java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2214) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2263) at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:519) at net.sf.hibernate.impl.SessionImpl.readObject(SessionImpl.java:446) at java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2214) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1411) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236) at net.sf.hibernate.util.SerializationHelper.deserialize(SerializationHelper.java:190) ... 14 more --------------------------------------------------------------------- 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-12-24 16:50:26
|
The following comment has been added to this issue:
Author: Leonid Shlyapnikov
Created: Wed, 24 Dec 2003 10:49 AM
Body:
Pardon,
I looked into jboss server.log with full DEBUG info and saw all that I needed. ConsoleAppeder is configured to append messages with INFO priority. I think my improvement issur should be closed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-577
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-577
Summary: hibernate.show_sql improvement
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Versions:
2.1.1
Assignee:
Reporter: Leonid Shlyapnikov
Created: Wed, 24 Dec 2003 10:30 AM
Updated: Wed, 24 Dec 2003 10:49 AM
Environment: Linux version 2.4.21-144-smp4G (ro...@i3...) (gcc version 3.3.1 (SuSE Linux)) #1 SMP Fri Nov 14 00:07:01 UTC 2003;
jdk 1.4.2; jboss-3.2.2;
Description:
It would be more useful if hibernate logged its SQL queries in more details. I mean symbols '?' in the logged query. The real values would help to determine problems. BTW, TopLink logs SQL queries fully :)
A part of show_sql log:
18:42:14,506 INFO [STDOUT] Hibernate: insert into RequestInfo (DurationMeasurementId, FromDate, Duration, EnterDate, ModificationDate, ProlongationOpportunity, RequestInfoDescription, RequestId, RequestInfoID) values (?, ?, ?, ?, ?, ?, ?, ?, ?)
bash: syntax error near unexpected token `('
shl@shl:~/javalib/hibernate-2.1/src> 18:42:14,506 INFO [STDOUT] Hibernate: insert into Demand (Commission, PriceFrom, PriceTo, RequestInfoId) values (?, ?, ?, ?)
bash: syntax error near unexpected token `('
shl@shl:~/javalib/hibernate-2.1/src> 18:42:24,759 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 22P02
bash: 18:42:24,759: command not found
shl@shl:~/javalib/hibernate-2.1/src> 18:42:24,759 ERROR [JDBCExceptionReporter] ERROR: invalid input syntax for integer: "\254\355\000\005sr\000!ru.incom.solaris.common.UniqueKey8\344\2432{\016\316T\002\000\001L\000\003keyt\000\020Ljava/lang/Long;xpsr\000\016java.lang.Long;\213\344\220\314\217#\337\002\000\001J\000\005valuexr\000\020java.lang.Number\206\254\225\035\013\224\340\213\002\000\000xp\000\000\000\000\000\000\000\002"
---------------------------------------------------------------------
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-12-24 16:31:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-577 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-577 Summary: hibernate.show_sql improvement Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Versions: 2.1.1 Assignee: Reporter: Leonid Shlyapnikov Created: Wed, 24 Dec 2003 10:30 AM Updated: Wed, 24 Dec 2003 10:30 AM Environment: Linux version 2.4.21-144-smp4G (ro...@i3...) (gcc version 3.3.1 (SuSE Linux)) #1 SMP Fri Nov 14 00:07:01 UTC 2003; jdk 1.4.2; jboss-3.2.2; Description: It would be more useful if hibernate logged its SQL queries in more details. I mean symbols '?' in the logged query. The real values would help to determine problems. BTW, TopLink logs SQL queries fully :) A part of show_sql log: 18:42:14,506 INFO [STDOUT] Hibernate: insert into RequestInfo (DurationMeasurementId, FromDate, Duration, EnterDate, ModificationDate, ProlongationOpportunity, RequestInfoDescription, RequestId, RequestInfoID) values (?, ?, ?, ?, ?, ?, ?, ?, ?) bash: syntax error near unexpected token `(' shl@shl:~/javalib/hibernate-2.1/src> 18:42:14,506 INFO [STDOUT] Hibernate: insert into Demand (Commission, PriceFrom, PriceTo, RequestInfoId) values (?, ?, ?, ?) bash: syntax error near unexpected token `(' shl@shl:~/javalib/hibernate-2.1/src> 18:42:24,759 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 22P02 bash: 18:42:24,759: command not found shl@shl:~/javalib/hibernate-2.1/src> 18:42:24,759 ERROR [JDBCExceptionReporter] ERROR: invalid input syntax for integer: "\254\355\000\005sr\000!ru.incom.solaris.common.UniqueKey8\344\2432{\016\316T\002\000\001L\000\003keyt\000\020Ljava/lang/Long;xpsr\000\016java.lang.Long;\213\344\220\314\217#\337\002\000\001J\000\005valuexr\000\020java.lang.Number\206\254\225\035\013\224\340\213\002\000\000xp\000\000\000\000\000\000\000\002" --------------------------------------------------------------------- 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-12-24 11:38:34
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 24 Dec 2003 5:37 AM
See HB-566
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-561
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-561
Summary: Add of sessionFactory evict methods to JMX MBean
Type: Improvement
Status: Closed
Priority: Minor
Resolution: DUPLICATE
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: William Drai
Created: Wed, 17 Dec 2003 6:06 AM
Updated: Wed, 24 Dec 2003 5:37 AM
Description:
It would be really useful for system administrators to be able to call the evictXXX methods of the sessionFactory from the JMX MBean, when the database has been manually updated.
---------------------------------------------------------------------
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-12-24 11:38:33
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 24 Dec 2003 5:37 AM
See HB-566
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-560
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-560
Summary: Caching configuration with same class mapped in many sessionFactories
Type: Improvement
Status: Closed
Priority: Trivial
Resolution: DUPLICATE
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: William Drai
Created: Wed, 17 Dec 2003 6:01 AM
Updated: Wed, 24 Dec 2003 5:37 AM
Description:
I'm sorry to reopen this issue but I still have a small problem.
I have the same class mapped in three differents session factories to three different MySQL databases.
Everything works (now with EHCache) BUT I am not able to define different cache configurations for the three cache instances because the cache region name is the same (it is the class name).
This is also true for all cache providers.
Moreover I have not tried yet the replicated cache but I don't see how the replication could be able to identify the correct cache instance in the remote server if all three have the same region name.
For the moment I implemented a wrapper CacheProvider which just adds the session factory property 'cache.region_prefix' before the region name and added this property to the Hibernate JMX MBean.
It would be a lot easier to configure if this was directly configured in hibernate. This is really trivial and I hope it could be useful for other people.
Thanks.
William
---------------------------------------------------------------------
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-12-24 11:37:28
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-570 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-570 Summary: EHCache Optional? Type: Bug Status: Closed Priority: Minor Resolution: REJECTED Project: Hibernate2 Components: core Versions: 2.1 final Assignee: Reporter: Prasad Khandekar Created: Fri, 19 Dec 2003 7:45 AM Updated: Wed, 24 Dec 2003 5:36 AM Environment: Windows 2000, JDK 1.4, Tomcat 4.1.24, Oracle 8i Description: The readme.txt file from Hibernate 2.1 final source archive says that the ehcache.jar file is optional. But the default settings makes the presence of this jar file mandetory. The code in buildSettings of SettingsFactory class defaults to ehcache provider and throws an exception. (It is possible to override this by setting use_query_cache property to false in hibernate.properties.) Is this jar is really necessary? If yes please provide an indication for the same. --------------------------------------------------------------------- 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-12-24 11:37:26
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-567 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-567 Summary: NullPointerException when using "select new" on constructor with native types Type: Bug Status: Closed Priority: Minor Resolution: REJECTED Project: Hibernate2 Components: core Versions: 2.1.1 Assignee: Reporter: Shorn Tolley Created: Wed, 17 Dec 2003 7:38 PM Updated: Wed, 24 Dec 2003 5:36 AM Environment: Win2k, JDK 1.4.2, HB 2.1.1 Description: When my DTO object that I am "Select new"'ing into has a constructor that takes native types, I get the error attached. If my DTO has a ctor which takes wrapper types, the code works. If it has both, then Hibernate seems to prefer the native version, and I get the error. I tried implementing the native-type ctor in two ways, using the "this" keyword to delegate to the wrapper-type ctor or with direct calls to the setter methods on the DTO. Didn't seem to make any difference. Exception: [junit] Testcase: testFindDocumentsByCaseDTOsWithEmptyCriteria(nrm.clas.persistence.document.test.DocumentPersistenceManagerTest): Caused an ERROR [junit] Error finding documents by case [junit] nrm.clas.persistence.PersistenceLayerException: Error finding documents by case [junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [junit] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [junit] at java.lang.reflect.Constructor.newInstance(Constructor.java:274) [junit] at nrm.clas.ExceptionUtil.instantiateException(ExceptionUtil.java:89) [junit] at nrm.clas.ExceptionUtil.createNestedException(ExceptionUtil.java:127) [junit] at nrm.clas.ExceptionUtil.createPersistenceLayerException(ExceptionUtil.java:312) [junit] at nrm.clas.ExceptionUtil.createPersistenceLayerException(ExceptionUtil.java:291) [junit] at nrm.clas.persistence.document.DocumentPersistenceManagerImpl.findDocumentsByCaseDTOs(DocumentPersistenceManagerImpl.java:162) [junit] at nrm.clas.persistence.document.test.DocumentPersistenceManagerTest.testFindDocumentsByCaseDTOsWithEmptyCriteria(DocumentPersistenceManagerTest.java:45) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at nrm.clas.test.ClasTestCase.run(ClasTestCase.java:508) [junit] Caused by: nrm.clas.common.persistence.PersistenceException: find [junit] at nrm.clas.persistence.BasePersistenceManagerImpl.handleError(BasePersistenceManagerImpl.java:97) [junit] at nrm.clas.persistence.BasePersistenceManagerImpl.handleError(BasePersistenceManagerImpl.java:116) [junit] at nrm.clas.persistence.BasePersistenceManagerImpl.find(BasePersistenceManagerImpl.java:365) [junit] at nrm.clas.persistence.document.DocumentPersistenceManagerImpl.findDocumentsByCaseDTOs(DocumentPersistenceManagerImpl.java:159) [junit] ... 16 more [junit] Caused by: net.sf.hibernate.QueryException: could not instantiate: class nrm.clas.dto.document.CaseDocumentDTO [junit] at net.sf.hibernate.hql.QueryTranslator.getResultColumnOrRow(QueryTranslator.java:993) [junit] at net.sf.hibernate.loader.Loader.doQuery(Loader.java:221) [junit] at net.sf.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:132) [junit] at net.sf.hibernate.loader.Loader.doList(Loader.java:949) [junit] at net.sf.hibernate.loader.Loader.list(Loader.java:940) [junit] at net.sf.hibernate.hql.QueryTranslator.list(QueryTranslator.java:833) [junit] at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1475) [junit] at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1454) [junit] at nrm.clas.persistence.BasePersistenceManagerImpl.find(BasePersistenceManagerImpl.java:359) [junit] ... 17 more [junit] Caused by: java.lang.NullPointerException [junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [junit] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [junit] at java.lang.reflect.Constructor.newInstance(Constructor.java:274) [junit] at net.sf.hibernate.hql.QueryTranslator.getResultColumnOrRow(QueryTranslator.java:990) [junit] ... 25 more --------------------------------------------------------------------- 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-12-24 11:35:30
|
The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 24 Dec 2003 5:34 AM
Body:
Would you create a patch, please? TIA...
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-19
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HBI-19
Summary: Exception clarity: AbstractEntityPersister:970
Type: Improvement
Status: Unassigned
Priority: Trivial
Project: Hibernate 1.2
Assignee:
Reporter: Brian Topping
Created: Wed, 24 Dec 2003 12:03 AM
Updated: Wed, 24 Dec 2003 5:34 AM
Description:
It would be nice if this MappingException message contained the name of the field that was duplicated.
---------------------------------------------------------------------
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-12-24 06:06:33
|
The following comment has been added to this issue:
Author: Brian Topping
Created: Wed, 24 Dec 2003 12:04 AM
Body:
If it wasn't clear from the title, this is on line 970 of the 2.1 source. (it's rather late here... :)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-19
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HBI-19
Summary: Exception clarity: AbstractEntityPersister:970
Type: Improvement
Status: Unassigned
Priority: Trivial
Project: Hibernate 1.2
Assignee:
Reporter: Brian Topping
Created: Wed, 24 Dec 2003 12:03 AM
Updated: Wed, 24 Dec 2003 12:04 AM
Description:
It would be nice if this MappingException message contained the name of the field that was duplicated.
---------------------------------------------------------------------
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-12-24 06:04:33
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-19 Here is an overview of the issue: --------------------------------------------------------------------- Key: HBI-19 Summary: Exception clarity: AbstractEntityPersister:970 Type: Improvement Status: Unassigned Priority: Trivial Project: Hibernate 1.2 Assignee: Reporter: Brian Topping Created: Wed, 24 Dec 2003 12:03 AM Updated: Wed, 24 Dec 2003 12:03 AM Description: It would be nice if this MappingException message contained the name of the field that was duplicated. --------------------------------------------------------------------- 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-12-23 15:09:26
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-576 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-576 Summary: problem to find hibernate.cfg.xml Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: belcore walter Created: Tue, 23 Dec 2003 9:08 AM Updated: Tue, 23 Dec 2003 9:08 AM Environment: hibernate 2.01, oc4j applciation server, oracle database Description: the getConfigurationInputStream method (Configuration class) load hibernate.cfg.xml with Environment.class.getResourceAsStream(nameresource). This can cause any problem with class loader (specially if you have call hibernate from a library shared for many web application) . I think that the correct code is : InputStream stream = Thread.currentThread().getContextClassLoader().getResourceAsStream(resource); --------------------------------------------------------------------- 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-12-23 11:53:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-575 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-575 Summary: ManagedConnectionFactoryImpl missing a config property Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Assignee: Reporter: attila lendvai Created: Tue, 23 Dec 2003 5:52 AM Updated: Tue, 23 Dec 2003 5:52 AM Description: ManagedConnectionFactoryImpl.java is missing this: Index: ManagedConnectionFactoryImpl.java =================================================================== RCS file: /cvsroot/hibernate/Hibernate2/src/net/sf/hibernate/jca/ManagedConnectionFactoryImpl.java,v retrieving revision 1.4 diff -u -r1.4 ManagedConnectionFactoryImpl.java --- ManagedConnectionFactoryImpl.java 15 Jun 2003 12:45:06 -0000 1.4 +++ ManagedConnectionFactoryImpl.java 23 Dec 2003 11:48:32 -0000 @@ -135,6 +135,7 @@ final Properties hibProperties = new Properties(); // @todo load this.properties hibProperties.setProperty(Environment.DIALECT, dialect); + hibProperties.setProperty(Environment.DATASOURCE, datasourceJndi); Configuration cfg = new Configuration().addProperties(hibProperties); --------------------------------------------------------------------- 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-12-22 20:12:25
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-574 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-574 Summary: SchemaExport/Update ant tasks should fail if a SQLException occurs Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Versions: 2.0.3 Assignee: Reporter: Rajesh Patel Created: Mon, 22 Dec 2003 2:12 PM Updated: Mon, 22 Dec 2003 2:12 PM Environment: Windows Description: When a sql exception occurs, both net.sf.hibernate.tool.hbm2ddl.SchemaExportTask and net.sf.hibernate.tool.hbm2ddl.SchemaUpdateTask do not fail, there should be a way to configure these tasks to report failure back to ant similar to that java task. It has a failonerror that halts the build. In the SchemaExport/SchemaUpdate classes it would be fairly simple to continue to ignore exceptions while dropping the tables, but to rethrow the sql exception when running the schema in. --------------------------------------------------------------------- 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-12-22 00:34:26
|
The following comment has been added to this issue:
Author: Shorn Tolley
Created: Sun, 21 Dec 2003 6:33 PM
Body:
Yeah, primitive types, those guys.
You're right, it is a result of nulls coming in from the query, and that can't really be allowed for ctors with primitive arguments (I'd much rather an NPE instead of setting 0 or something like that).
It's just a little hard to figure out what's going on at first though.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-567
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-567
Summary: NullPointerException when using "select new" on constructor with native types
Type: Bug
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Shorn Tolley
Created: Wed, 17 Dec 2003 7:38 PM
Updated: Sun, 21 Dec 2003 6:33 PM
Environment: Win2k, JDK 1.4.2, HB 2.1.1
Description:
When my DTO object that I am "Select new"'ing into has a constructor that takes native types, I get the error attached.
If my DTO has a ctor which takes wrapper types, the code works.
If it has both, then Hibernate seems to prefer the native version, and I get the error.
I tried implementing the native-type ctor in two ways, using the "this" keyword to delegate to the wrapper-type ctor or with direct calls to the setter methods on the DTO. Didn't seem to make any difference.
Exception:
[junit] Testcase: testFindDocumentsByCaseDTOsWithEmptyCriteria(nrm.clas.persistence.document.test.DocumentPersistenceManagerTest): Caused an ERROR
[junit] Error finding documents by case
[junit] nrm.clas.persistence.PersistenceLayerException: Error finding documents by case
[junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[junit] at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
[junit] at nrm.clas.ExceptionUtil.instantiateException(ExceptionUtil.java:89)
[junit] at nrm.clas.ExceptionUtil.createNestedException(ExceptionUtil.java:127)
[junit] at nrm.clas.ExceptionUtil.createPersistenceLayerException(ExceptionUtil.java:312)
[junit] at nrm.clas.ExceptionUtil.createPersistenceLayerException(ExceptionUtil.java:291)
[junit] at nrm.clas.persistence.document.DocumentPersistenceManagerImpl.findDocumentsByCaseDTOs(DocumentPersistenceManagerImpl.java:162)
[junit] at nrm.clas.persistence.document.test.DocumentPersistenceManagerTest.testFindDocumentsByCaseDTOsWithEmptyCriteria(DocumentPersistenceManagerTest.java:45)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at nrm.clas.test.ClasTestCase.run(ClasTestCase.java:508)
[junit] Caused by: nrm.clas.common.persistence.PersistenceException: find
[junit] at nrm.clas.persistence.BasePersistenceManagerImpl.handleError(BasePersistenceManagerImpl.java:97)
[junit] at nrm.clas.persistence.BasePersistenceManagerImpl.handleError(BasePersistenceManagerImpl.java:116)
[junit] at nrm.clas.persistence.BasePersistenceManagerImpl.find(BasePersistenceManagerImpl.java:365)
[junit] at nrm.clas.persistence.document.DocumentPersistenceManagerImpl.findDocumentsByCaseDTOs(DocumentPersistenceManagerImpl.java:159)
[junit] ... 16 more
[junit] Caused by: net.sf.hibernate.QueryException: could not instantiate: class nrm.clas.dto.document.CaseDocumentDTO
[junit] at net.sf.hibernate.hql.QueryTranslator.getResultColumnOrRow(QueryTranslator.java:993)
[junit] at net.sf.hibernate.loader.Loader.doQuery(Loader.java:221)
[junit] at net.sf.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:132)
[junit] at net.sf.hibernate.loader.Loader.doList(Loader.java:949)
[junit] at net.sf.hibernate.loader.Loader.list(Loader.java:940)
[junit] at net.sf.hibernate.hql.QueryTranslator.list(QueryTranslator.java:833)
[junit] at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1475)
[junit] at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1454)
[junit] at nrm.clas.persistence.BasePersistenceManagerImpl.find(BasePersistenceManagerImpl.java:359)
[junit] ... 17 more
[junit] Caused by: java.lang.NullPointerException
[junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[junit] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[junit] at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
[junit] at net.sf.hibernate.hql.QueryTranslator.getResultColumnOrRow(QueryTranslator.java:990)
[junit] ... 25 more
---------------------------------------------------------------------
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-12-19 18:27:08
|
The following issue has been updated:
Updater: John Kristian (mailto:jkr...@do...)
Date: Fri, 19 Dec 2003 12:26 PM
Comment:
In addition to improving performance, this change might avoid bugs. For example, bug.log (attached) shows a problem that occurred after Session.refresh called a entity property getter whose implementation did interesting things with Hibernate (to select the best localized value among several from an internationalized database). This problem is avoided if Session.refresh doesn't call ReferenceDomain.getName() before loading.
Changes:
Attachment changed to bug.log
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-573&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-573
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-573
Summary: Don't get all property values when visiting collections
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 final
Assignee:
Reporter: John Kristian
Created: Fri, 19 Dec 2003 11:43 AM
Updated: Fri, 19 Dec 2003 12:26 PM
Environment: JBoss, Windows XP, Microsoft SQL Server
Description:
Please eliminate wasted motion in the collection visitor classes; specifically, don't get the values of properties that can't contain collections. CollectionVisitor.patch [attached] is a rough implementation that works. Perhaps it might be improved to use persister.optimizer.getPropertyValues if persister has an optimizer.
---------------------------------------------------------------------
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-12-19 18:01:10
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-571 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-571 Summary: net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections Type: Bug Status: Closed Priority: Major Resolution: DUPLICATE Project: Hibernate2 Versions: 2.1 Assignee: Reporter: Raider Yang Created: Fri, 19 Dec 2003 9:41 AM Updated: Fri, 19 Dec 2003 12:00 PM Environment: tomcat+mysql Description: at java.lang.Thread.run(Thread.java:536) net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections at net.sf.hibernate.impl.SessionImpl.prepareCollectionForUpdate(SessionImpl.java:2635) at net.sf.hibernate.impl.SessionImpl.updateReachableCollection(SessionImpl.java:2556) at net.sf.hibernate.impl.SessionImpl.updateReachable(SessionImpl.java:2577) at net.sf.hibernate.impl.SessionImpl.updateReachables(SessionImpl.java:2682) at net.sf.hibernate.impl.SessionImpl.flushEntities(SessionImpl.java:2259) at net.sf.hibernate.impl.SessionImpl.flushEverything(SessionImpl.java:2017) at net.sf.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:1560) at net.sf.hibernate.impl.SessionImpl.getQueries(SessionImpl.java:1372) at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1332) at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1322) --------------------------------------------------------------------- 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-12-19 17:52:08
|
The following comment has been added to this issue:
Author: Gavin King
Created: Fri, 19 Dec 2003 11:51 AM
Body:
Yeah, this is quite useless unless you post some actual code to reproduce this, along with the actual release version of Hibernate 2.1. Note that there were changes b/w 2.1beta6 and 2.1final in this respect, and that assertion failures like this also occur if you perform some incorrect session handling, or do something else illegal in get/set methods or in callbacks.
So 99% likely, this is a problem with *your* code.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-572
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-572
Summary: net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1
Assignee:
Reporter: Raider Yang
Created: Fri, 19 Dec 2003 9:41 AM
Updated: Fri, 19 Dec 2003 11:51 AM
Environment: tomcat+mysql
Description:
at java.lang.Thread.run(Thread.java:536)
net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections
at net.sf.hibernate.impl.SessionImpl.prepareCollectionForUpdate(SessionImpl.java:2635)
at net.sf.hibernate.impl.SessionImpl.updateReachableCollection(SessionImpl.java:2556)
at net.sf.hibernate.impl.SessionImpl.updateReachable(SessionImpl.java:2577)
at net.sf.hibernate.impl.SessionImpl.updateReachables(SessionImpl.java:2682)
at net.sf.hibernate.impl.SessionImpl.flushEntities(SessionImpl.java:2259)
at net.sf.hibernate.impl.SessionImpl.flushEverything(SessionImpl.java:2017)
at net.sf.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:1560)
at net.sf.hibernate.impl.SessionImpl.getQueries(SessionImpl.java:1372)
at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1332)
at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1322)
---------------------------------------------------------------------
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-12-19 17:44:09
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-573 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-573 Summary: Don't get all property values when visiting collections Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 final Assignee: Reporter: John Kristian Created: Fri, 19 Dec 2003 11:43 AM Updated: Fri, 19 Dec 2003 11:43 AM Environment: JBoss, Windows XP, Microsoft SQL Server Description: Please eliminate wasted motion in the collection visitor classes; specifically, don't get the values of properties that can't contain collections. CollectionVisitor.patch [attached] is a rough implementation that works. Perhaps it might be improved to use persister.optimizer.getPropertyValues if persister has an optimizer. --------------------------------------------------------------------- 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-12-19 17:44:09
|
The following issue has been updated:
Updater: John Kristian (mailto:jkr...@do...)
Date: Fri, 19 Dec 2003 11:44 AM
Changes:
Attachment changed to CollectionVisitor.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-573&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-573
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-573
Summary: Don't get all property values when visiting collections
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 final
Assignee:
Reporter: John Kristian
Created: Fri, 19 Dec 2003 11:43 AM
Updated: Fri, 19 Dec 2003 11:44 AM
Environment: JBoss, Windows XP, Microsoft SQL Server
Description:
Please eliminate wasted motion in the collection visitor classes; specifically, don't get the values of properties that can't contain collections. CollectionVisitor.patch [attached] is a rough implementation that works. Perhaps it might be improved to use persister.optimizer.getPropertyValues if persister has an optimizer.
---------------------------------------------------------------------
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-12-19 15:53:11
|
The following comment has been added to this issue:
Author: Max Rydahl Andersen
Created: Fri, 19 Dec 2003 9:53 AM
Body:
eh - yes ? A stacktrace does not help much if no code, mapping file etc. is available ?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-572
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-572
Summary: net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1
Assignee:
Reporter: Raider Yang
Created: Fri, 19 Dec 2003 9:41 AM
Updated: Fri, 19 Dec 2003 9:53 AM
Environment: tomcat+mysql
Description:
at java.lang.Thread.run(Thread.java:536)
net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections
at net.sf.hibernate.impl.SessionImpl.prepareCollectionForUpdate(SessionImpl.java:2635)
at net.sf.hibernate.impl.SessionImpl.updateReachableCollection(SessionImpl.java:2556)
at net.sf.hibernate.impl.SessionImpl.updateReachable(SessionImpl.java:2577)
at net.sf.hibernate.impl.SessionImpl.updateReachables(SessionImpl.java:2682)
at net.sf.hibernate.impl.SessionImpl.flushEntities(SessionImpl.java:2259)
at net.sf.hibernate.impl.SessionImpl.flushEverything(SessionImpl.java:2017)
at net.sf.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:1560)
at net.sf.hibernate.impl.SessionImpl.getQueries(SessionImpl.java:1372)
at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1332)
at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1322)
---------------------------------------------------------------------
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-12-19 15:42:17
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-572 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-572 Summary: net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 Assignee: Reporter: Raider Yang Created: Fri, 19 Dec 2003 9:41 AM Updated: Fri, 19 Dec 2003 9:41 AM Environment: tomcat+mysql Description: at java.lang.Thread.run(Thread.java:536) net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections at net.sf.hibernate.impl.SessionImpl.prepareCollectionForUpdate(SessionImpl.java:2635) at net.sf.hibernate.impl.SessionImpl.updateReachableCollection(SessionImpl.java:2556) at net.sf.hibernate.impl.SessionImpl.updateReachable(SessionImpl.java:2577) at net.sf.hibernate.impl.SessionImpl.updateReachables(SessionImpl.java:2682) at net.sf.hibernate.impl.SessionImpl.flushEntities(SessionImpl.java:2259) at net.sf.hibernate.impl.SessionImpl.flushEverything(SessionImpl.java:2017) at net.sf.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:1560) at net.sf.hibernate.impl.SessionImpl.getQueries(SessionImpl.java:1372) at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1332) at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1322) --------------------------------------------------------------------- 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-12-19 15:42:17
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-571 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-571 Summary: net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 Assignee: Reporter: Raider Yang Created: Fri, 19 Dec 2003 9:41 AM Updated: Fri, 19 Dec 2003 9:41 AM Environment: tomcat+mysql Description: at java.lang.Thread.run(Thread.java:536) net.sf.hibernate.AssertionFailure: Hibernate has a bug processing collections at net.sf.hibernate.impl.SessionImpl.prepareCollectionForUpdate(SessionImpl.java:2635) at net.sf.hibernate.impl.SessionImpl.updateReachableCollection(SessionImpl.java:2556) at net.sf.hibernate.impl.SessionImpl.updateReachable(SessionImpl.java:2577) at net.sf.hibernate.impl.SessionImpl.updateReachables(SessionImpl.java:2682) at net.sf.hibernate.impl.SessionImpl.flushEntities(SessionImpl.java:2259) at net.sf.hibernate.impl.SessionImpl.flushEverything(SessionImpl.java:2017) at net.sf.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:1560) at net.sf.hibernate.impl.SessionImpl.getQueries(SessionImpl.java:1372) at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1332) at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1322) --------------------------------------------------------------------- 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-12-19 15:17:08
|
Message: The following issue has been closed. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-569 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-569 Summary: SchemaExport generates incorrect schema separator for MySQL Type: Bug Status: Closed Priority: Major Resolution: REJECTED Project: Hibernate2 Components: toolset Versions: 2.1.1 Assignee: Reporter: Jos Annevelink Created: Fri, 19 Dec 2003 7:35 AM Updated: Fri, 19 Dec 2003 9:17 AM Description: While everything worked ok on 2.0.3 I saw incorrect DDL/SQL being generated while trying to switch my application to 2.1.1 The DDL generated reads "... dbname_tablename ..." whereas it should read "... dbname.tablename ..." (dot for separator instead of underscore). It seems a method MySQLDialect.getSchemaSeparator() was added which returns a '_' instead of a '.'. --------------------------------------------------------------------- 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-12-19 14:37:11
|
The following comment has been added to this issue:
Author: Prasad Khandekar
Created: Fri, 19 Dec 2003 8:36 AM
Body:
Sorry I have just gone through the code and found out that it is not possible to override this settings by hibernate.cache.use_query_cache property. The correct way would be setting the name of hibernate.cache.provider_class in hibernate configuration file.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-570
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-570
Summary: EHCache Optional?
Type: Bug
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1 final
Assignee:
Reporter: Prasad Khandekar
Created: Fri, 19 Dec 2003 7:45 AM
Updated: Fri, 19 Dec 2003 8:36 AM
Environment: Windows 2000, JDK 1.4, Tomcat 4.1.24, Oracle 8i
Description:
The readme.txt file from Hibernate 2.1 final source archive says that the ehcache.jar file is optional. But the default settings makes the presence of this jar file mandetory. The code in buildSettings of SettingsFactory class defaults to ehcache provider and throws an exception.
(It is possible to override this by setting use_query_cache property to false in hibernate.properties.)
Is this jar is really necessary? If yes please provide an indication for the same.
---------------------------------------------------------------------
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.
