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-09-13 20:33:52
|
The following issue has been updated:
Updater: Michael Gloegl (mailto:gl...@ok...)
Date: Sat, 13 Sep 2003 3:31 PM
Changes:
Attachment changed to Example.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-334&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-334
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-334
Summary: Example-API automatic wildcards and fix for ignoreCase
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: Michael Gloegl
Created: Sat, 13 Sep 2003 3:31 PM
Updated: Sat, 13 Sep 2003 3:31 PM
Description:
After applying this patch, when enabling like with Example, you can pass a flag which will automatically add wildcards to all properties.
Example.create(exampleObject).enableLike(Example.MATCH_ANYWHERE)
will take all values of exampleObject and add % at the beginning and the end.
This patch also fixes Example.ignoreCase() which does not work yet.
---------------------------------------------------------------------
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-09-13 20:33:52
|
The following issue has been updated:
Updater: Michael Gloegl (mailto:gl...@ok...)
Date: Sat, 13 Sep 2003 3:32 PM
Changes:
Attachment changed to FooBarTest.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-334&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-334
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-334
Summary: Example-API automatic wildcards and fix for ignoreCase
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: Michael Gloegl
Created: Sat, 13 Sep 2003 3:31 PM
Updated: Sat, 13 Sep 2003 3:32 PM
Description:
After applying this patch, when enabling like with Example, you can pass a flag which will automatically add wildcards to all properties.
Example.create(exampleObject).enableLike(Example.MATCH_ANYWHERE)
will take all values of exampleObject and add % at the beginning and the end.
This patch also fixes Example.ignoreCase() which does not work yet.
---------------------------------------------------------------------
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-09-13 20:31:52
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-334 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-334 Summary: Example-API automatic wildcards and fix for ignoreCase Type: Improvement Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Michael Gloegl Created: Sat, 13 Sep 2003 3:31 PM Updated: Sat, 13 Sep 2003 3:31 PM Description: After applying this patch, when enabling like with Example, you can pass a flag which will automatically add wildcards to all properties. Example.create(exampleObject).enableLike(Example.MATCH_ANYWHERE) will take all values of exampleObject and add % at the beginning and the end. This patch also fixes Example.ignoreCase() which does not work yet. --------------------------------------------------------------------- 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-09-13 14:35:29
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sat, 13 Sep 2003 9:35 AM
I implemented something very similar to this, (after looking over this patch). The main differences are
(1) do things at the property level with a new access attribute
(2) designed a pluggable PropertyAccessor interface
Thanks!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-270
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-270
Summary: Ability to choose accessors/ fields/both for population
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 final
Versions:
2.0.2
Assignee:
Reporter: Vladimir Dozen
Created: Sat, 16 Aug 2003 2:46 PM
Updated: Sat, 13 Sep 2003 9:35 AM
Environment: Any
Description:
Hibernate uses setters/getters to access properties of objects.
This may lead to unconvinience, unstability or performance hit in
various situations. The patch provides ability for programmer to
choose what method will use Hibernate: accessors (default), fields,
accessors-then-fields, fields-then-accessors. Developer may explicitely
mark specific classes as accessible via fields or methods.
Example: unconvinience:
We have a lot of POD structures (i.e. structures which has all
fields as public final) and forcing to provide getters/setters
is just doesn't give any profit and simply unconvinient (BTW: and impossible without removing final).
Example: unstablity:
Often setter contain some code to check validity of the passed
arguments. That's fine when the system that uses Hibernate is the
only way to DB. But, when integrating with legacy systems, we cannot
be sure incorrect data cannot get into DB. When Hibernate attempt then
load such object from the DB using that checking setter, it will get
exception and will fail. The same applies also for multi-row selects and even to loading objects of another types that has (non-lazy) references to broken object. System becomes mostly unusable.
Example: performance:
Validity checks in setters can sometimes take significant amount of
time. For example, time to check if the word exists in some dictionary
grows as log2(n), and can be large enough. Multi-row selects makes the
things even worse.
Workarounds like making alternative set of accessors are ugly, and
make the code messed.
The patch adds hibernate.conf option hibernate.access.order that can
have following values: "accessors-only" (default), "fields-only",
"fields-then-accessors" and "accessors-then-fields". According to
the option Hibernate will scan the object for properties or setters/getter. Plus, using special marker interfaces ReflectHelper.AccessibleViaMethodsOnly, ... programmer can mark specific class as to be accessible using specific method.
---------------------------------------------------------------------
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-09-13 06:21:27
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sat, 13 Sep 2003 1:20 AM
Thanks. Actually this only affected CVS, not the current release. Good you found it!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-333
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-333
Summary: NullPointer in SessionFactoryImpl.close
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 final
Versions:
2.1 beta 3
Assignee:
Reporter: Ralph Schaer
Created: Sat, 13 Sep 2003 12:39 AM
Updated: Sat, 13 Sep 2003 1:20 AM
Environment: windows xp, java 1.4.2_01, hibernate cvs version 09/13/2003
Description:
When my program calls the close method of SessionFactory it throws a NullPointerException in line 520
queryCache.destroy();
queryCache is null when query cache is disabled.
see the constructor
if ( settings.isQueryCacheEnabled() ) {
queryCache = new QueryCache( settings.getCacheProvider(), properties );
}
else {
queryCache = null;
}
---------------------------------------------------------------------
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-09-13 05:39:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-333 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-333 Summary: NullPointer in SessionFactoryImpl.close Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Ralph Schaer Created: Sat, 13 Sep 2003 12:39 AM Updated: Sat, 13 Sep 2003 12:39 AM Environment: windows xp, java 1.4.2_01, hibernate cvs version 09/13/2003 Description: When my program calls the close method of SessionFactory it throws a NullPointerException in line 520 queryCache.destroy(); queryCache is null when query cache is disabled. see the constructor if ( settings.isQueryCacheEnabled() ) { queryCache = new QueryCache( settings.getCacheProvider(), properties ); } else { queryCache = null; } --------------------------------------------------------------------- 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-09-13 03:45:32
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 12 Sep 2003 10:44 PM
This exception occured when a <joined-subclass> of a versioned entity had _only_ a collection and no other properties.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-332
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-332
Summary: Calling session.save() twice on a timestamped object causes exception
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1 final
Versions:
2.1 beta 3
Assignee:
Reporter: Greg Barton
Created: Fri, 12 Sep 2003 5:46 PM
Updated: Fri, 12 Sep 2003 10:44 PM
Environment: MySQL 4.1, Connector/J 3.0.8
Description:
A mapped object with a timestamp and a set mapped causes a SQLException. (Due to a null SQL statement being sent to the JDBC driver.)
NOTE:
See attached tar. Run the ant script for a demonstration. (Target "sql_generate" to create DDL for database, "demo_broken" to see exception, "demo_fixed" to see normal execution.) The only jar I included was the hibernate-tools.jar, as I compiled it from a CVS snapshot.
Versions used:
Hibernate 2.1 beta 3
Hibernate tools from CVS snapshot 2003-09-04
---------------------------------------------------------------------
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: Hanasaki J. <han...@ha...> - 2003-09-13 03:36:12
|
Hibernate seems to normally look for schemata files in the same directory as the .class of the corresponding bean. XDcolet has been configured to put all the files in /WEB-INF/hibernate/schema How can hibernate be told to look in there? The preference would be to somehow have the hibernate.cfg file automatically generated by XDoclet (not sure how to do this or if it can be done) -- ================================================================= = Management is doing things right; leadership is doing the = = right things. - Peter Drucker = =_______________________________________________________________= = http://www.sun.com/service/sunps/jdc/javacenter.pdf = = www.sun.com | www.javasoft.com | http://www.sun.com/sunone = ================================================================= |
|
From: <leg...@at...> - 2003-09-13 02:32:27
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 12 Sep 2003 9:30 PM
It does.
If you check your log, you will see an ERROR, where the XML validation fails.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-328
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-328
Summary: NullPointerException from buildSessionFactory
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.2
Assignee:
Reporter: Loren Rosen
Created: Fri, 12 Sep 2003 11:52 AM
Updated: Fri, 12 Sep 2003 9:30 PM
Environment: MacOS X 10.1.5 JDK 1.3
Description:
I got a NullPointerException with this stack trace:
Exception in thread "main" java.lang.NullPointerException
at net.sf.hibernate.collection.CollectionPersister.<init>(CollectionPersister.java:191)
at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:216)
at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:627)
at com.loren.Report.startHibernate(Report.java:44)
at com.loren.Report.main(Report.java:88)
Turned out the problem was a missing 'index' attribute on a 'map' in a hibernate mapping file:
<map name="documentAuthors" table="document_author" sort="com.loren.DocumentAuthorComparator" inverse="true" lazy="true">
<key column="document"/>
<index column="place" type="int"/>
<one-to-many class="com.loren.DocumentAuthor"/>
</map>
(This is the corrected version.)
Hibernate should give a specific error message in this situation.
---------------------------------------------------------------------
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-09-13 02:30:27
|
The following comment has been added to this issue:
Author: Gavin King
Created: Fri, 12 Sep 2003 9:30 PM
Body:
There is an example exactly like this in the test suite. So you'll have to submit actual code, so I can reproduce this.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-331
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-331
Summary: Problem with create Query
Type: Bug
Status: Unassigned
Priority: Critical
Project: Hibernate2
Components:
core
Versions:
2.0.1
Assignee:
Reporter: Osvaldo Andres Cifuentes
Created: Fri, 12 Sep 2003 5:26 PM
Updated: Fri, 12 Sep 2003 5:26 PM
Environment: windows 2000 server spanish,xdoclet,jboss 3.2.1,jdk 1.4.2,oracle 9i Enterprise Edition
Description:
I'm using Session createQuery from Hibernate 2.0.1, the source look like this:
List tipos = new ArrayList();
for(int lu=0;lu<ti.length;lu++)
tipos.add(ti[lu]);
Query q = sess.createQuery("from Cliente cliente where cliente.identificacionPK.tipoIdentidad in (:tiposIdentidad) and cliente.identificacionPK.identidad like (:identidad)");
q.setParameterList("tiposIdentidad", tipos);
q.setString("identidad", i+"%");
List client=q.list();
with this code i put the query on a list
for (int k=1;k<=client.size();k++){
Cliente cli=(Cliente)client.get(k);
log.debug(cli.getNombres());
}
the Hibernate generated SQL source is OK. (I already tasted)
But when I look the client list, i can see that the first data is overwriting the others, The same
numbers of times than must have the query.
For example:
*The expected result:
id name
__________
1 a
2 b
3 c
4 d
5 e
6 f
7 g
*The actual result:
id name
__________
1 a
1 a
1 a
1 a
1 a
1 a
1 a
I hope any one can help me, I'll be very thankful
---------------------------------------------------------------------
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-09-12 22:48:27
|
The following issue has been updated:
Updater: Greg Barton (mailto:gre...@ya...)
Date: Fri, 12 Sep 2003 5:46 PM
Changes:
Attachment changed to code.tar.gz
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-332&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-332
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-332
Summary: Calling session.save() twice on a timestamped object causes exception
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.1 beta 3
Assignee:
Reporter: Greg Barton
Created: Fri, 12 Sep 2003 5:46 PM
Updated: Fri, 12 Sep 2003 5:46 PM
Environment: MySQL 4.1, Connector/J 3.0.8
Description:
A mapped object with a timestamp and a set mapped causes a SQLException. (Due to a null SQL statement being sent to the JDBC driver.)
NOTE:
See attached tar. Run the ant script for a demonstration. (Target "sql_generate" to create DDL for database, "demo_broken" to see exception, "demo_fixed" to see normal execution.) The only jar I included was the hibernate-tools.jar, as I compiled it from a CVS snapshot.
Versions used:
Hibernate 2.1 beta 3
Hibernate tools from CVS snapshot 2003-09-04
---------------------------------------------------------------------
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-09-12 22:46:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-332 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-332 Summary: Calling session.save() twice on a timestamped object causes exception Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Versions: 2.1 beta 3 Assignee: Reporter: Greg Barton Created: Fri, 12 Sep 2003 5:46 PM Updated: Fri, 12 Sep 2003 5:46 PM Environment: MySQL 4.1, Connector/J 3.0.8 Description: A mapped object with a timestamp and a set mapped causes a SQLException. (Due to a null SQL statement being sent to the JDBC driver.) NOTE: See attached tar. Run the ant script for a demonstration. (Target "sql_generate" to create DDL for database, "demo_broken" to see exception, "demo_fixed" to see normal execution.) The only jar I included was the hibernate-tools.jar, as I compiled it from a CVS snapshot. Versions used: Hibernate 2.1 beta 3 Hibernate tools from CVS snapshot 2003-09-04 --------------------------------------------------------------------- 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-09-12 22:27:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-331 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-331 Summary: Problem with create Query Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Osvaldo Andres Cifuentes Created: Fri, 12 Sep 2003 5:26 PM Updated: Fri, 12 Sep 2003 5:26 PM Environment: windows 2000 server spanish,xdoclet,jboss 3.2.1,jdk 1.4.2,oracle 9i Enterprise Edition Description: I'm using Session createQuery from Hibernate 2.0.1, the source look like this: List tipos = new ArrayList(); for(int lu=0;lu<ti.length;lu++) tipos.add(ti[lu]); Query q = sess.createQuery("from Cliente cliente where cliente.identificacionPK.tipoIdentidad in (:tiposIdentidad) and cliente.identificacionPK.identidad like (:identidad)"); q.setParameterList("tiposIdentidad", tipos); q.setString("identidad", i+"%"); List client=q.list(); with this code i put the query on a list for (int k=1;k<=client.size();k++){ Cliente cli=(Cliente)client.get(k); log.debug(cli.getNombres()); } the Hibernate generated SQL source is OK. (I already tasted) But when I look the client list, i can see that the first data is overwriting the others, The same numbers of times than must have the query. For example: *The expected result: id name __________ 1 a 2 b 3 c 4 d 5 e 6 f 7 g *The actual result: id name __________ 1 a 1 a 1 a 1 a 1 a 1 a 1 a I hope any one can help me, I'll be very thankful --------------------------------------------------------------------- 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-09-12 18: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-330 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-330 Summary: Loading mapping files from ManagedConnectionFactoryImpl in WebLogic Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.1 Assignee: Reporter: Ethan Wolf Created: Fri, 12 Sep 2003 1:31 PM Updated: Fri, 12 Sep 2003 1:31 PM Environment: Windows 2000, WebLogic 8.1 (on windows 2000) Description: ManagedConnectionFactoryImpl.initialize() passes the contextClassLoader from the thread to load the mapping files in Configuration.addResource. This works fine (in both JBoss and WebLogic) IF the mapping files are on the class path of the application server. It also works on JBoss when the mapping files are packaged with the connector deployment (-ds.xml). (The mapping files are found through JBoss' UnifiedClassLoader architecture.) However, in WebLogic, the configuration files are not found when they are packaged with the individual deployment. This seems to be because the thread that deploys the component corresponds to the root thread on the application server, and therefore uses the Launcher$AppClassLoader. The actual class loader used to load the deployed connector (GenericClassLoader) is managed by the deploymer components of weblogic. Changin the class loader passed to Configuration.addResource by the ManagedConnectionFactoryImpl to getClass().getClassLoader() seems to result in the desired ability to load the mapping files from the deployment directory. Since the ManagedConnectionFactoryImpl is only used when deploying to an application server, I would assume that this has no adverse affects and it seems correct, but these class loader issues are quite mind boggling. --------------------------------------------------------------------- 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-09-12 17:45:27
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-329 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-329 Summary: <property name="default_schema"> Does not propagate to non-Table types Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: Eric Fenderbosch Created: Fri, 12 Sep 2003 12:44 PM Updated: Fri, 12 Sep 2003 12:44 PM Description: When specifing <property name="default_schema">eousr</property> in cfg.xml, this does not have any effect on sequence names. Example: <id name="id" type="java.lang.Long"> <column name="TARIFF_ID"/> <generator class="sequence"> <param name="sequence">tariff_seq</param> </generator> </id> However, if the schema is specified in the mapping using <hibernate-mapping schema="eousr"> or <class name="com.fedex.cc.objectlib.tariff.TariffState" table="TARIFF" schema="eousr"> then it works as expected. --------------------------------------------------------------------- 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-09-12 17:01:27
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 12 Sep 2003 12:00 PM
OK then, please report this to the CGLIB guys.
http://cglib.sf.net
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-327
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-327
Summary: memory leak
Type: Bug
Status: Closed
Priority: Critical
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: Bostjan Dolenc
Created: Fri, 12 Sep 2003 10:42 AM
Updated: Fri, 12 Sep 2003 12:00 PM
Environment: Oracle 9i, WebLogic 8.1 SP1, JDK 1.4.2_01 (also on JDK 1.4.1_03)
Description:
Symptoms:
Deploy and undeploy the application about 10 times under WL 8.1 with -Xmx512m. I get OutOfMemoryException on the deploy.
I ran OptimizeIt Profiler over the app. server. It seems that Hibernate caches which contain instrumented classes are not released.
Application:
J2EE application, consisting of few SLSBs and uses Hibernate to access the database. Hibernate startup/shutdown is managed by WebLogic's ApplicationLifecycleListner. That's a listener which receives events on application startup and shutdown. I first thought that the issue was with the classloader. We used to initialize Hibernate inside WebLogic's classloader, but I get OutOfMemoryException even when using classloader of our application.
---------------------------------------------------------------------
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-09-12 16:53:28
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-328 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-328 Summary: NullPointerException from buildSessionFactory Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0.2 Assignee: Reporter: Loren Rosen Created: Fri, 12 Sep 2003 11:52 AM Updated: Fri, 12 Sep 2003 11:52 AM Environment: MacOS X 10.1.5 JDK 1.3 Description: I got a NullPointerException with this stack trace: Exception in thread "main" java.lang.NullPointerException at net.sf.hibernate.collection.CollectionPersister.<init>(CollectionPersister.java:191) at net.sf.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:216) at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:627) at com.loren.Report.startHibernate(Report.java:44) at com.loren.Report.main(Report.java:88) Turned out the problem was a missing 'index' attribute on a 'map' in a hibernate mapping file: <map name="documentAuthors" table="document_author" sort="com.loren.DocumentAuthorComparator" inverse="true" lazy="true"> <key column="document"/> <index column="place" type="int"/> <one-to-many class="com.loren.DocumentAuthor"/> </map> (This is the corrected version.) Hibernate should give a specific error message in this situation. --------------------------------------------------------------------- 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-09-12 16:31:28
|
The following comment has been added to this issue:
Author: Bostjan Dolenc
Created: Fri, 12 Sep 2003 11:30 AM
Body:
Yep, CGLIB classes. I'll try to post some text from OptimizeIt on Monday.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-327
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-327
Summary: memory leak
Type: Bug
Status: Unassigned
Priority: Critical
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: Bostjan Dolenc
Created: Fri, 12 Sep 2003 10:42 AM
Updated: Fri, 12 Sep 2003 10:42 AM
Environment: Oracle 9i, WebLogic 8.1 SP1, JDK 1.4.2_01 (also on JDK 1.4.1_03)
Description:
Symptoms:
Deploy and undeploy the application about 10 times under WL 8.1 with -Xmx512m. I get OutOfMemoryException on the deploy.
I ran OptimizeIt Profiler over the app. server. It seems that Hibernate caches which contain instrumented classes are not released.
Application:
J2EE application, consisting of few SLSBs and uses Hibernate to access the database. Hibernate startup/shutdown is managed by WebLogic's ApplicationLifecycleListner. That's a listener which receives events on application startup and shutdown. I first thought that the issue was with the classloader. We used to initialize Hibernate inside WebLogic's classloader, but I get OutOfMemoryException even when using classloader of our application.
---------------------------------------------------------------------
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-09-12 16:21:28
|
The following comment has been added to this issue:
Author: Gavin King
Created: Fri, 12 Sep 2003 11:20 AM
Body:
Which contain _what_? "instrumented classes"??
Are you talking about CGLIB cache of generated classes?
something else?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-327
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-327
Summary: memory leak
Type: Bug
Status: Unassigned
Priority: Critical
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
Assignee:
Reporter: Bostjan Dolenc
Created: Fri, 12 Sep 2003 10:42 AM
Updated: Fri, 12 Sep 2003 10:42 AM
Environment: Oracle 9i, WebLogic 8.1 SP1, JDK 1.4.2_01 (also on JDK 1.4.1_03)
Description:
Symptoms:
Deploy and undeploy the application about 10 times under WL 8.1 with -Xmx512m. I get OutOfMemoryException on the deploy.
I ran OptimizeIt Profiler over the app. server. It seems that Hibernate caches which contain instrumented classes are not released.
Application:
J2EE application, consisting of few SLSBs and uses Hibernate to access the database. Hibernate startup/shutdown is managed by WebLogic's ApplicationLifecycleListner. That's a listener which receives events on application startup and shutdown. I first thought that the issue was with the classloader. We used to initialize Hibernate inside WebLogic's classloader, but I get OutOfMemoryException even when using classloader of our application.
---------------------------------------------------------------------
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-09-12 16:03:27
|
The following comment has been added to this issue:
Author: John Kristian
Created: Fri, 12 Sep 2003 11:02 AM
Body:
Yes, with that change the same exception occurs and the preceding log entries are quite similar.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-321
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-321
Summary: could not create JCS region: NullPointerException
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee:
Reporter: John Kristian
Created: Tue, 9 Sep 2003 6:42 PM
Updated: Wed, 10 Sep 2003 7:58 PM
Environment: Windows XP Professional, JBoss 3, Microsoft SQL Server 2000
Description:
With Hibernate 2.0.3 (but not 2.0.2), the following error occurs.
2003-09-09 16:25:11,453 ERROR [net.sf.hibernate.cache.JCSCache] could not create JCS region
java.lang.NullPointerException
at org.apache.jcs.engine.memory.lru.LRUMemoryCache.update(LRUMemoryCache.java:116)
at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:241)
at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:200)
at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:311)
at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:279)
at net.sf.hibernate.cache.JCSCache.put(JCSCache.java:36)
at net.sf.hibernate.cache.ReadWriteCache.put(ReadWriteCache.java:64)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1966)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.assemble(EntityType.java:93)
at net.sf.hibernate.collection.Set.<init>(Set.java:94)
at net.sf.hibernate.type.SetType.assembleCachedCollection(SetType.java:36)
at net.sf.hibernate.collection.CollectionPersister.getCachedCollection(CollectionPersister.java:308)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:66)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.type.PersistentCollectionType.assemble(PersistentCollectionType.java:129)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:53)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:45)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1872)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.assemble(EntityType.java:93)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:53)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:45)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1872)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.assemble(EntityType.java:93)
at net.sf.hibernate.collection.Set.<init>(Set.java:94)
at net.sf.hibernate.type.SetType.assembleCachedCollection(SetType.java:36)
at net.sf.hibernate.collection.CollectionPersister.getCachedCollection(CollectionPersister.java:308)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:66)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.type.PersistentCollectionType.assemble(PersistentCollectionType.java:129)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:53)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:45)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1872)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.load(SessionImpl.java:1688)
at com.docent.lms.entities.reference.GeneratedUser$Factory.getById(GeneratedUser.java:456)
at com.docent.lms.web.Visit.getUser(Visit.java:252)
---------------------------------------------------------------------
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-09-12 15:56:29
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Fri, 12 Sep 2003 10:56 AM
fixed typo's and added them to cvs.
Please test'em - I can't ;)
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1
Assignee: Max Rydahl Andersen
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Fri, 12 Sep 2003 10:56 AM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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-09-12 15:42:28
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-327 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-327 Summary: memory leak Type: Bug Status: Unassigned Priority: Critical Project: Hibernate2 Components: core Versions: 2.1 beta 3 Assignee: Reporter: Bostjan Dolenc Created: Fri, 12 Sep 2003 10:42 AM Updated: Fri, 12 Sep 2003 10:42 AM Environment: Oracle 9i, WebLogic 8.1 SP1, JDK 1.4.2_01 (also on JDK 1.4.1_03) Description: Symptoms: Deploy and undeploy the application about 10 times under WL 8.1 with -Xmx512m. I get OutOfMemoryException on the deploy. I ran OptimizeIt Profiler over the app. server. It seems that Hibernate caches which contain instrumented classes are not released. Application: J2EE application, consisting of few SLSBs and uses Hibernate to access the database. Hibernate startup/shutdown is managed by WebLogic's ApplicationLifecycleListner. That's a listener which receives events on application startup and shutdown. I first thought that the issue was with the classloader. We used to initialize Hibernate inside WebLogic's classloader, but I get OutOfMemoryException even when using classloader of our application. --------------------------------------------------------------------- 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-09-12 07:37:29
|
The following issue has been updated:
Updater: Reha CENANI (mailto:rc...@bi...)
Date: Fri, 12 Sep 2003 2:37 AM
Comment:
Hi, excuse me for the delay. New dialects are attached.
Changes:
Attachment changed to dialects.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-293
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-293
Summary: Seperating InterBase and Firebird dialects
Type: Improvement
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
core
Assignee: Max Rydahl Andersen
Reporter: Reha CENANI
Created: Tue, 26 Aug 2003 6:46 AM
Updated: Fri, 12 Sep 2003 2:37 AM
Description:
At the begining, opensource Firebird (or FirebirdSQL) was based on the same source code of commercial InterBase. But during past three years, lots of improvements are done to the Firebird. Recent versions of these DBMSs have different features and statement syntaxes.
For example, their select offset/limit statement syntaxes are not compatible. Hibernate's recent InterbaseDialect select limit/offset feature is based on the Firebird's select statement syntax.
So, in order to prevent incompabilities and confussion, in addition to the InterbaseDialect, adding a new FirebirdDialect and seperating Firebird and InterBase features will be very helpfull.
---------------------------------------------------------------------
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-09-12 03:29:29
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 11 Sep 2003 10:28 PM
Body:
So the exception still occurs, even with that change?
Well, you need to submit actual working (broken) code, not code fragments. Code fragments are useless.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-321
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-321
Summary: could not create JCS region: NullPointerException
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee:
Reporter: John Kristian
Created: Tue, 9 Sep 2003 6:42 PM
Updated: Wed, 10 Sep 2003 7:58 PM
Environment: Windows XP Professional, JBoss 3, Microsoft SQL Server 2000
Description:
With Hibernate 2.0.3 (but not 2.0.2), the following error occurs.
2003-09-09 16:25:11,453 ERROR [net.sf.hibernate.cache.JCSCache] could not create JCS region
java.lang.NullPointerException
at org.apache.jcs.engine.memory.lru.LRUMemoryCache.update(LRUMemoryCache.java:116)
at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:241)
at org.apache.jcs.engine.control.CompositeCache.update(CompositeCache.java:200)
at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:311)
at org.apache.jcs.access.CacheAccess.put(CacheAccess.java:279)
at net.sf.hibernate.cache.JCSCache.put(JCSCache.java:36)
at net.sf.hibernate.cache.ReadWriteCache.put(ReadWriteCache.java:64)
at net.sf.hibernate.impl.SessionImpl.initializeEntity(SessionImpl.java:1966)
at net.sf.hibernate.loader.Loader.doFind(Loader.java:196)
at net.sf.hibernate.loader.Loader.loadEntity(Loader.java:587)
at net.sf.hibernate.loader.EntityLoader.load(EntityLoader.java:42)
at net.sf.hibernate.persister.EntityPersister.load(EntityPersister.java:396)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1889)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.assemble(EntityType.java:93)
at net.sf.hibernate.collection.Set.<init>(Set.java:94)
at net.sf.hibernate.type.SetType.assembleCachedCollection(SetType.java:36)
at net.sf.hibernate.collection.CollectionPersister.getCachedCollection(CollectionPersister.java:308)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:66)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.type.PersistentCollectionType.assemble(PersistentCollectionType.java:129)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:53)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:45)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1872)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.assemble(EntityType.java:93)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:53)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:45)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1872)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:1716)
at net.sf.hibernate.type.ManyToOneType.resolveIdentifier(ManyToOneType.java:62)
at net.sf.hibernate.type.EntityType.assemble(EntityType.java:93)
at net.sf.hibernate.collection.Set.<init>(Set.java:94)
at net.sf.hibernate.type.SetType.assembleCachedCollection(SetType.java:36)
at net.sf.hibernate.collection.CollectionPersister.getCachedCollection(CollectionPersister.java:308)
at net.sf.hibernate.type.PersistentCollectionType.getCollection(PersistentCollectionType.java:66)
at net.sf.hibernate.type.PersistentCollectionType.resolveIdentifier(PersistentCollectionType.java:177)
at net.sf.hibernate.type.PersistentCollectionType.assemble(PersistentCollectionType.java:129)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:53)
at net.sf.hibernate.impl.CacheEntry.assemble(CacheEntry.java:45)
at net.sf.hibernate.impl.SessionImpl.doLoad(SessionImpl.java:1872)
at net.sf.hibernate.impl.SessionImpl.doLoadByClass(SessionImpl.java:1757)
at net.sf.hibernate.impl.SessionImpl.load(SessionImpl.java:1688)
at com.docent.lms.entities.reference.GeneratedUser$Factory.getById(GeneratedUser.java:456)
at com.docent.lms.web.Visit.getUser(Visit.java:252)
---------------------------------------------------------------------
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-09-12 03:27:27
|
The following issue has been updated:
Updater: Gavin King (mailto:ga...@in...)
Date: Thu, 11 Sep 2003 10:26 PM
Comment:
This is not really a _bug_...
I agree that the current design, where CollectionPersister is a single class, rather than an interface, could be vastly improved.
Changes:
type changed from Bug
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-326&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-326
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-326
Summary: Persister assigned to a class not used when persisting a Set
Type: Improvement
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee:
Reporter: Nick Johnson
Created: Thu, 11 Sep 2003 4:56 PM
Updated: Thu, 11 Sep 2003 10:26 PM
Environment: JDK 1.4 on Win2k
Description:
When persisting a Set, the persister for the class defined within the Set is not used. For example, with a mapping like this:
<class name="foo" persister="FooPersister">
<!-- ... -->
<set name="relatedStuff">
<key column="related_stuff_key" />
<one-to-many class="bar" />
</set>
</class>
<class name="bar" persister="BarPersister">
<!-- ... -->
</class>
Operations on the set "relatedStuff" will result in SQL being generated rather than the necessary operations being handed off to BarPersister.
Another alternative or possible solution to this problem would be the ability to define a custom persister for Hibernate's collections classes; eg, "<set name="relatedStuff" persister="CustomSetPersister">"
This problem arose because we need to control how a many-to-many-style table is persisted (we use stored procedures to do inserts, updates and deletes). Because of the way the tables are normalized and because of the requirements of the system (arbitrary linkage between collections and the necessity of interoperating with existing infrastructure) the schema looks something like this:
Group
-----
group_id number primary key
(other attributes on group follow)
Group_member
------------
parent_group_id number (references the group_id in Group)
child_group_id number (ditto)
The original problem is that we've been unsuccessful in getting customized persistence for the Group_member table. Even creating a custom persister for the Group_member table still results in SQL getting generated rather than the custom persister being used.
This turns out to be a difficult thing to describe, so if what I've said isn't terribly clear, I'm more than happy to try to clarify ambiguities.
---------------------------------------------------------------------
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.
