Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: <leg...@at...> - 2003-10-14 05:25:20
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-397 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-397 Summary: Hibernate configuration DTD should not require mapping(s) Type: Bug Status: Unassigned Priority: Major Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: David Morris Created: Tue, 14 Oct 2003 12:24 AM Updated: Tue, 14 Oct 2003 12:24 AM Description: The hibernate-configuration dtd defines mapping as a 1-many relationship to mappings. This makes it impossible to use a session configuration without at least one mapping defined. I have attached a patch, however the change is trivial, just change mapping+ to mapping* in http://hibernate.sourceforge.net/hibernate-configuration-2.0.dtd (will this become 2.1?). --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-13 22:02:20
|
The following issue has been updated:
Updater: Rob Stokes (mailto:av...@ya...)
Date: Mon, 13 Oct 2003 5:00 PM
Comment:
Hope its in the correct format.
Changes:
Attachment changed to Validatable.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-396&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-396
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-396
Summary: hbm2java validate method code generation
Type: Patch
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
toolset
Versions:
2.0 final
Assignee:
Reporter: Rob Stokes
Created: Mon, 13 Oct 2003 4:59 PM
Updated: Mon, 13 Oct 2003 5:00 PM
Environment: Hibernate Extensions 2.0
Description:
This patch contains the code to generate the validate() method for classes that implement net.sf.hibernate.Validatable interface. The validate method will check nullablity and string lengths check based on the mapping file. As part of the nullability checks it also add static initializers for collection type variables. Any checks that fail will throw a ValidationFailure exception with a message loaded from a resource bundle created by ValidatableMessageRenderer. ValidatableMessageRenderer must be added to the config.xml used by hbm2java. The messages can then be modified to what ever you want them to say.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-13 22:00:20
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-396 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-396 Summary: hbm2java validate method code generation Type: Patch Status: Unassigned Priority: Minor Project: Hibernate2 Components: toolset Versions: 2.0 final Assignee: Reporter: Rob Stokes Created: Mon, 13 Oct 2003 4:59 PM Updated: Mon, 13 Oct 2003 4:59 PM Environment: Hibernate Extensions 2.0 Description: This patch contains the code to generate the validate() method for classes that implement net.sf.hibernate.Validatable interface. The validate method will check nullablity and string lengths check based on the mapping file. As part of the nullability checks it also add static initializers for collection type variables. Any checks that fail will throw a ValidationFailure exception with a message loaded from a resource bundle created by ValidatableMessageRenderer. ValidatableMessageRenderer must be added to the config.xml used by hbm2java. The messages can then be modified to what ever you want them to say. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-13 21:48:20
|
The following issue has been updated:
Updater: Jason Carreira (mailto:jas...@no...)
Date: Mon, 13 Oct 2003 4:47 PM
Comment:
This is an example of the issue. I haven't included the libraries, but all it needs are the standard hibernate jars and hsqldb.jar.
As you can see from the tests, this isn't a problem with session.find(), only session.load().
Changes:
Attachment changed to src.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-395&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-395
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-395
Summary: Lazy Initialization used even when collection mapping says lazy="false"
Type: Bug
Status: Unassigned
Priority: Blocker
Project: Hibernate2
Components:
core
Versions:
2.1 beta 3
2.1 beta 4
Assignee:
Reporter: Jason Carreira
Created: Mon, 13 Oct 2003 4:46 PM
Updated: Mon, 13 Oct 2003 4:47 PM
Environment: We use Oracle with WebLogic and WebSphere, but I've included a test case which fails as unit tests running against HSQL
Description:
If a child class has a Proxy (all the ones I've tested have themselves as the proxy class) and the parent class has a <set> mapping to the child class with lazy="false", then, if session.load(Parent.class, parentId) is called, then child collection will be lazily initialized. This doesn't happen with session.find(), for some reason.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-13 21:46:20
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-395 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-395 Summary: Lazy Initialization used even when collection mapping says lazy="false" Type: Bug Status: Unassigned Priority: Blocker Project: Hibernate2 Components: core Versions: 2.1 beta 3 2.1 beta 4 Assignee: Reporter: Jason Carreira Created: Mon, 13 Oct 2003 4:46 PM Updated: Mon, 13 Oct 2003 4:46 PM Environment: We use Oracle with WebLogic and WebSphere, but I've included a test case which fails as unit tests running against HSQL Description: If a child class has a Proxy (all the ones I've tested have themselves as the proxy class) and the parent class has a <set> mapping to the child class with lazy="false", then, if session.load(Parent.class, parentId) is called, then child collection will be lazily initialized. This doesn't happen with session.find(), for some reason. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-13 21:32:20
|
The following comment has been added to this issue:
Author: John Kristian
Created: Mon, 13 Oct 2003 4:31 PM
Body:
This problem was not solved by BatcherImpl.java -rv21beta4 (1.9.2.10). When using a WebLogic data source, a JDBC connection that is not closed may propagate an exception from getWarnings(); for example:
java.sql.SQLException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:118)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:127)
at weblogic.jdbc.wrapper.Connection.preInvocationHandler(Connection.java:67)
at weblogic.jdbc.wrapper.JTSConnection_com_jnetdirect_jsql_JSQLConnection.getWarnings(Unknown Source)
at net.sf.hibernate.impl.BatcherImpl.closeConnection(BatcherImpl.java:272)
at net.sf.hibernate.impl.SessionImpl.disconnect(SessionImpl.java:3285)
at net.sf.hibernate.impl.SessionImpl.close(SessionImpl.java:497)
at com.docent.lms.core.SessionInterceptor.closeHibernateSession(SessionInterceptor.java:98)
at com.docent.lms.core.TransactionImpl.closeHibernateSession(TransactionImpl.java:431)
at com.docent.lms.core.TransactionImpl.close(TransactionImpl.java:359)
To mitigate the problem, I suggest (and am using) this patch:
==== src/net/sf/hibernate/impl/BatcherImpl.java ====
@@ -272,6 +272,11 @@
JDBCExceptionReporter.logWarnings( conn.getWarnings() );
conn.clearWarnings();
}
+ }
+ catch (SQLException sqle) {
+ log.warn("Cannot log warnings: " + sqle.getMessage());
+ }
+ try {
factory.getConnectionProvider().closeConnection(conn);
}
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-360
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-360
Summary: WebLogic DataSource doesn't permit conn.getWarnings after commit
Type: Patch
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1 beta 4
Versions:
2.0.2
Assignee:
Reporter: John Kristian
Created: Wed, 24 Sep 2003 1:49 PM
Updated: Thu, 25 Sep 2003 4:24 PM
Environment: WebLogic 7, Windows 2000, Microsoft SQL Server
Description:
SessionFactoryImpl.closeConnection fails to close the JDBC conection, because an exception propagates from conn.getWarnings, because the connection is already closed (as a side-effect of commiting the JTA transaction, I suppose). This patch solves the problem:
==== src/net/sf/hibernate/impl/SessionFactoryImpl.java ====
@@ -403,6 +403,11 @@
try {
JDBCExceptionReporter.logWarnings( conn.getWarnings() );
conn.clearWarnings();
+ }
+ catch (SQLException sqle) {
+ log.warn("Cannot log warnings: " + sqle.getMessage());
+ }
+ try {
connections.closeConnection(conn);
}
catch (SQLException sqle) {
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-13 17:07:20
|
Message:
The following issue has been re-assigned.
Assignee: Christian Bauer (mailto:chr...@hi...)
Assigner: Gavin King (mailto:ga...@in...)
Date: Mon, 13 Oct 2003 12:06 PM
Comment:
You want this Christian?
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-391
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-391
Summary: Udated bat files in the tools - defined HIBERNATE_HOME
Type: Patch
Status: Assigned
Priority: Major
Project: Hibernate2
Components:
toolset
Assignee: Christian Bauer
Reporter: Mukund Pragasam
Created: Fri, 10 Oct 2003 8:31 AM
Updated: Mon, 13 Oct 2003 12:06 PM
Environment: run the tools (like hbm2java) from any other IDE like JBuilder.
Description:
In the tools/bin we have
class2hbm.bat
ddl2hbm.bat
hbm2java.bat
setenv.bat
all the above bat files need to know HIBERNATE_HOME
they were using relative path to get it. When I run these tools from JBuilder, they were not working because of the relative path.
I extracted hibernate-extensions-2.0.zip in the hibernate home directory.
So I had the directory structure like
avalon
bin
build.bat
build.xml
changelog.txt
demo.bat
demo.sh
doc
hibernate2.jar
hibernate_logo.gif
lgpl.txt
lib
readme.txt
src
tools
I have modified the files to get HIBERNATE_HOME from the environment variables.
For example
if "%HIBERNATE_HOME%"=="" goto noHIBERNATEHome
call %HIBERNATE_HOME%\tools\bin\setenv.bat
java -cp %CP% net.sf.hibernate.tool.class2hbm.MapGenerator %*
if not "%HIBERNATE_HOME%"=="" goto end
:noHIBERNATEHome
echo HIBERNATE_HOME is not set. Please set HIBERNATE_HOME.
:end
set HIBERNATE_HOME
I can send this to the group and they can update this in their copy. I can send all the bat files with similar updates.
I am not sure how this works. Will this be Assigned To me? or Do I need to send the modified bat files in a mail...?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-13 14:16:20
|
The following comment has been added to this issue:
Author: Christopher D Riccio
Created: Mon, 13 Oct 2003 9:16 AM
Body:
Nevermind... My bad.
Eclipse was pulling from an old jar. After flushing it and importing fresh it worked fine.
Thanks guys!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-353
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-353
Summary: query.setProperty( Object ) assumes HQL
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Christopher D Riccio
Created: Mon, 22 Sep 2003 12:58 PM
Updated: Sat, 27 Sep 2003 7:07 PM
Environment: DB2 Database
Description:
Here's what I have.
QUERY
select {d.*}
from department {d}
where {d}.deptno = :deptno
passing in an object (Department) which has a
private String deptno;
on it.
Getting the following Exception:
net.sf.hibernate.QueryException: in expected: {d} [select {d.*}
from department {d}
where {d}.deptno = :deptno]
{d} is defined in my query object.
When I do
Query.setString( "deptno", department.getDeptno() );
The query executes correctly.
After looking deeper into this.
Seems as if it is handling the Native sql call as HQL.
The query dies after parsing "department."
it's expecting a class path, ( saw indexOf( '.' ) so I assume that is what was going on). Then it sets expectingIn to true. The next thing it sees is {d} and it chokes on it.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-13 12:46:20
|
The following comment has been added to this issue:
Author: Christopher D Riccio
Created: Mon, 13 Oct 2003 7:45 AM
Body:
Was this in the beta 4 release.
I'm still getting the same error.
in expected: {tableAlias}
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-353
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-353
Summary: query.setProperty( Object ) assumes HQL
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1
Versions:
2.1
Assignee: Max Rydahl Andersen
Reporter: Christopher D Riccio
Created: Mon, 22 Sep 2003 12:58 PM
Updated: Sat, 27 Sep 2003 7:07 PM
Environment: DB2 Database
Description:
Here's what I have.
QUERY
select {d.*}
from department {d}
where {d}.deptno = :deptno
passing in an object (Department) which has a
private String deptno;
on it.
Getting the following Exception:
net.sf.hibernate.QueryException: in expected: {d} [select {d.*}
from department {d}
where {d}.deptno = :deptno]
{d} is defined in my query object.
When I do
Query.setString( "deptno", department.getDeptno() );
The query executes correctly.
After looking deeper into this.
Seems as if it is handling the Native sql call as HQL.
The query dies after parsing "department."
it's expecting a class path, ( saw indexOf( '.' ) so I assume that is what was going on). Then it sets expectingIn to true. The next thing it sees is {d} and it chokes on it.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-13 09:12:23
|
Message:
The following issue has been closed.
Resolver: Daniel Bradby
Date: Mon, 13 Oct 2003 4:11 AM
Fixed
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-383
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-383
Summary: websphere 5 transaction manager lookup
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Hibernate2
Components:
core
Fix Fors:
2.1
Versions:
2.1 beta 4
Assignee: Daniel Bradby
Reporter: Edina Pimp
Created: Tue, 7 Oct 2003 11:54 AM
Updated: Mon, 13 Oct 2003 4:11 AM
Environment: WebSphere Platform 5.0 [BASE 5.0.2]; Win2k; WSAD; JDK1.3.1
Description:
Newest version of the WebSphereTransactionManagerLookup fails under WebSphere 5. Class com.ibm.ejs.jts.jta.JTSXA - which is the default class - remains available in the classpath so it's found and Hibernate assumes a WAS4 environment.
When 'getTransactionManager' is invoked on the WAS5 version of JTSXA, a NoSuchMethod exception is thrown, caught, and rethrown as a HibernateException. The correct method is instance().
This worked in 2.1b3 because the exception handling just happened to line up the right way.
Maybe it's reasonable to break out different WebSphere4TransactionManagerLookup and WebSphere5TransactionManagerLookup classes, ugly as it sounds.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-12 17:55:20
|
The following comment has been added to this issue:
Author: Lars Hoss
Created: Sun, 12 Oct 2003 12:54 PM
Body:
I do not agree on this, sorry. If the DTD file reflects the 2.1 version shouldn't it be called hibernate-mapping-2.1.dtd instead of hibernate-mapping-2.0.dtd?
Hibernate 2.0 for example DOES NOT understand the attribute outer-join for the map attribute but the online version of the hibernate-mapping-2.0.dtd file says so. The documentation of the Hibernate 2.0.x version uses the following doctype:
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD 2.0//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd">
In Intellij IDEA it is possible to download this DTD file for XML validation while you are typing. Therefore I thought that outer-joins are possible for maps because the DTD says so. But when I started my application I've got an error because Hibernate 2.0 doesn't understand the outer-join attribute. If you look at the DTD file provided with the hibernate-2.0.3.jar file you will see that map DOES NOT have an outer-join attribute.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-385
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-385
Summary: Online hibernate-mapping-2.0.dtd differs from dtd in jar file
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee:
Reporter: Lars Hoss
Created: Wed, 8 Oct 2003 5:11 AM
Updated: Sun, 12 Oct 2003 12:34 PM
Description:
The online version of the mapping dtd differs from the dtd in the jar file (hibernate 2.0.3). For example the element set has the attribute outer-join in the online version but not in the jar file version. I guess that the online version matches 2.1 beta?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-12 17:35:22
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 12 Oct 2003 12:34 PM
The 2.1 mapping dtd is diff to 2.0.x.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-385
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-385
Summary: Online hibernate-mapping-2.0.dtd differs from dtd in jar file
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee:
Reporter: Lars Hoss
Created: Wed, 8 Oct 2003 5:11 AM
Updated: Sun, 12 Oct 2003 12:34 PM
Description:
The online version of the mapping dtd differs from the dtd in the jar file (hibernate 2.0.3). For example the element set has the attribute outer-join in the online version but not in the jar file version. I guess that the online version matches 2.1 beta?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-12 17:35:22
|
Message: The following issue has been re-assigned. Assignee: Max Rydahl Andersen (mailto:xa...@xa...) --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-387 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-387 Summary: hbm2java: addX(T x)/removeX(T x) methods generation in one-to-many relation class Type: Improvement Status: Assigned Priority: Major Project: Hibernate2 Components: toolset Versions: 2.0.3 Assignee: Max Rydahl Andersen Reporter: venkat dosapati Created: Wed, 8 Oct 2003 9:14 AM Updated: Sun, 12 Oct 2003 12:33 PM Description: I was generating the java source files from mapping. I have two classes Workspace and Asset. Workspace-to-Asset is one-to-many association and Asset-to-Workspace is many-to-one association. I did the required mapping for these 2 classes in my mapping file. But when I generate the classes the class 'Workspace' is not having the expected methods. I was expecting 'addAsset(Asset)' & 'removeAsset(Asset)' methods in Workspace class. But the generated class 'Workspace' was not having them. I feel Workspace class should have the following methods in addition to setAssets(List), getAssets(): public class Workspace { private ArrayList assets; public void addAsset(Asset _asset){ if(assets==null) assets=new ArrayList(); _asset.setWorkspace(this); assets.add(_asset); } public void removeAsset(Asset _asset){ if(assets==null)return; _asset.setWorkspace(null); assets.remove(_asset); } } I also feel it is better to have 'getAsset(Object assetId)' method in Workspace class in case of composition relation. thanks dosapati --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-12 17:24:21
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 12 Oct 2003 12:23 PM
Hibernate does not have any memory leaks. Please do not report these kind of problems here. We have a user forum!
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-386
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-386
Summary: Hibernate crashes while populate large tables
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1
2.0.3
Assignee:
Reporter: Jeff Gager
Created: Wed, 8 Oct 2003 6:18 AM
Updated: Sun, 12 Oct 2003 12:23 PM
Environment: Dell 2Ghz Pentium 4 512MB RAM Running Windows XP.
Java 1.4.2
Eclipse 2.1.1
Description:
I am trying to write a simple java application that reads a large number of records from a Oracle database (using JDBC) and loads them into a mySQL database through hibernate.
The application crashes with java.lang.OutOfMemoryError.
As the application runs I can see it steadilly using up memory until it eventually falls over. I am commiting the Transaction, closing the Session and creating a new Session and Transaction every 1000 records. I think hibernate is either failing to release some kind of resource, or it is performing some action on the existing data before creating each record which is consuming more memory as more records are created.
I am not sure how to proceed, your help would be much appreciated.
Source follows;
package X
lots of import's
public class XLoader {
private static Logger log = Logger.getLogger("X.XLoader");
public static void main(String[] args) throws Throwable {
log.info("Processing starting at " + new Date());
Connection conn = null;
try {
// Create the JDBC Driver
final OracleDriver driver = new OracleDriver();
// Load the Oracle JDBC driver
DriverManager.registerDriver(driver);
// Establish Read-only JDBC Connection to the PAS database
conn = (Connection)DriverManager.getConnection("jdbc:oracle:oci8:@XXX", "XXX", "XXX");
conn.setAutoCommit(false);
// Loading...
loadPerson(conn);
log.info("Processing completed at " + new Date());
} catch (Throwable e) {
log.fatal("Unhandled Exception - processing halted\n" + e.toString());
throw e;
} finally {
conn.close();
System.exit(1);
log.info("Finished at " + new Date());
}
}
private static void loadPerson(Connection conn) throws Throwable {
log.info("Processing people at " + new Date());
// Declare statment and result set
PreparedStatement stmt = null;
ResultSet rset = null;
Session session = null;
Transaction tx = null;
SessionFactory sf = new Configuration().configure("/XX.xml").buildSessionFactory();
try {
// Load people
String sql = "BIG SELECT STATEMENT HERE";
log.info("Reading people at " + new Date());
stmt = conn.prepareStatement(sql,
ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY);
rset = stmt.executeQuery();
if (rset.getFetchSize() < 1)
throw new SQLException("No People found");
session = sf.openSession();
tx = session.beginTransaction();
log.info("Loading people at " + new Date());
int counter = 0;
String lastPayroll = "";
Payroll payroll = null;
while (rset.next()) {
// Create new payrolls as we find them
String thisPayroll = rset.getString(1);
if (!thisPayroll.equals(lastPayroll)) {
payroll = new Payroll();
payroll.setName(rset.getString(1));
payroll.setFrequency(rset.getString(2));
payroll.setStatus(rset.getString(3));
payroll.setFirstPaydate(rset.getDate(4));
payroll.setNextPaydate(rset.getDate(5));
payroll.setPrevPaydate(rset.getDate(6));
payroll.setRunDate(rset.getDate(7));
payroll.setAccountName(rset.getString(8));
payroll.setAccountNumber(rset.getInt(9));
payroll.setSortcode(rset.getInt(10));
payroll.setBacsName(rset.getString(11));
payroll.setBacsNumber(rset.getInt(12));
ArrayList payrollMemberships = new ArrayList();
payroll.setMemberships(payrollMemberships);
session.save(payroll);
}
lastPayroll = thisPayroll;
// Create people
Person person = new Person();
person.setReference(rset.getString(13));
person.setSurname(rset.getString(14));
person.setSex(rset.getString(15).charAt(0));
person.setForenames(rset.getString(16));
person.setInitials(rset.getString(17));
person.setTitle(rset.getString(18));
person.setNiNumber(rset.getString(19));
person.setBirth(rset.getDate(20));
ArrayList personMemberships = new ArrayList();
person.setMemberships(personMemberships);
ArrayList personAddresses = new ArrayList();
person.setAddresses(personAddresses);
session.save(person);
// Create memberships
Membership membership = new Membership();
membership.setStart(rset.getDate(21));
membership.setStatus("Paying");
membership.setPerson(person);
membership.setPayroll(payroll);
person.addMembership(membership);
payroll.addMembership(membership);
session.save(membership);
// Create addresses
Address address = new Address();
address.setStart(new Date());
address.setLine1(rset.getString(22));
address.setLine2(rset.getString(23));
address.setTown(rset.getString(24));
address.setCounty(rset.getString(25));
address.setPostcode(rset.getString(26));
address.setPerson(person);
person.addAddress(address);
session.save(address);
if ((++counter % 1000) == 0) {
tx.commit();
long payid = payroll.getId().longValue();
session.close();
session = sf.openSession();
tx = session.beginTransaction();
payroll = (Payroll)session.load(Payroll.class, new Long(payid));
log.info("Loaded " + counter);
}
}
tx.commit();
session.close();
sf.close();
log.info("Total People Loaded " + counter);
rset.close();
stmt.close();
// Handle errors
} catch (Throwable e) {
log.fatal(e.getMessage(), e);
rset.close();
stmt.close();
if (sf != null) sf.close();
if (session != null) session.close();
if (tx != null) tx.rollback();
throw e;
}
log.info("Finished processing people at " + new Date());
}
}
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-12 17:22:20
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 12 Oct 2003 12:20 PM
This is a FAQ. Please read the documentation.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-388
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-388
Summary: composite id with saveOrUpdate not updating, duplicate key
Type: Bug
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee:
Reporter: Michael Lowe
Created: Wed, 8 Oct 2003 1:28 PM
Updated: Sun, 12 Oct 2003 12:20 PM
Environment: sql200
Description:
I attempt to update a row with a composite id using saveOrUpdate and get "Violation of PRIMARY KEY constraint: Cannot insert duplicate key in object."
If I change the method to update, it works fine, unless, of course I try to insert, then save works.
I tried all combinations of unsaved-value, to no avail.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-12 17:20:21
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 12 Oct 2003 12:19 PM
This is intended, since a synthetic composite key is non-meaningful. Anyway it can be done using the "audit info custom type" pattern.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-389
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-389
Summary: DTD does not allow 'generator'-tag in 'composite-id', whereas Hibernate does and works perfect
Type: Bug
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee:
Reporter: Jan-Allard Slurink
Created: Thu, 9 Oct 2003 2:37 AM
Updated: Sun, 12 Oct 2003 12:19 PM
Environment: W2K SP4, JDK 1.3
Description:
Consider this part of the mapping-file:
<class name="AdresModel" table="ADRES">
<composite-id name="adresnr" class="AdresnrModel">
<key-property name="adresnr"/>
<generator class="AdresnrPKGenerator">
<param name="sequence">SEQ_ADRES</param>
</generator>
</composite-id>
...
...
I have a wrapper named AdresnrModel (with only one field) for my custom PK, and I want to use a PK-Generator mapped to an oracle sequence with it.
The error I get is this:
2003-10-08 15:00:33,309 ERROR net.sf.hibernate.util.XMLHelper - Error parsing XML: XML InputStream(20)
org.xml.sax.SAXParseException: Element "composite-id" does not allow "generator" here.
void org.apache.crimson.parser.Parser2.error(java.lang.String, java.lang.Object[])
Despite the SAXParseException, Hibernate WORKS and does perfectly what I want.
So the bug is: Either the DTD does not support the above Hibernate feature, OR hibernate allows this feature whereas it shouldn't allow it.
My best guess is that the DTD should be updated to the current capabilities of Hibernate
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-12 17:18:24
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 12 Oct 2003 12:16 PM
this was already fixed in CVS
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-390
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-390
Summary: XmlDatabinder.bindAll() is broken
Type: Bug
Status: Closed
Priority: Major
Resolution: DUPLICATE
Project: Hibernate2
Versions:
2.1
Assignee:
Reporter: Sayeed Anjum
Created: Thu, 9 Oct 2003 9:37 PM
Updated: Sun, 12 Oct 2003 12:16 PM
Description:
We have a silly error in the following method:
public Databinder bindAll(Collection objects) {
objects.addAll(objects);
return this;
}
we need to change line #1 above to:
this.objects.addAll(objects);
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-12 17:16:20
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sun, 12 Oct 2003 12:15 PM
This is a completely useless issue report, since it gives no information about the situation in which the problem occurred. Since it is almost certainly a problem with the user's mapping file, this issue should be redirected to the user forum.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-392
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-392
Summary: NPE in net.sf.hibernate.cfg.Binder.bindCollectionSecondPass
Type: Bug
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0.3
Assignee:
Reporter: Ingo Schildmann
Created: Fri, 10 Oct 2003 10:47 AM
Updated: Sun, 12 Oct 2003 12:15 PM
Description:
java.lang.NullPointerException
at net.sf.hibernate.cfg.Binder.bindCollectionSecondPass(Binder.java:1076)
at net.sf.hibernate.cfg.Binder.bindSetSecondPass(Binder.java:923)
at net.sf.hibernate.cfg.Binder$SetSecondPass.secondPass(Binder.java:1187)
at net.sf.hibernate.cfg.Binder$SecondPass.doSecondPass(Binder.java:1135)
at net.sf.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:497)
at net.sf.hibernate.cfg.Configuration.generateDropSchemaScript(Configuration.java:352)
at net.sf.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:51)
at net.sf.hibernate.tool.hbm2ddl.SchemaExportTask.getSchemaExport(SchemaExportTask.java:198)
at net.sf.hibernate.tool.hbm2ddl.SchemaExportTask.execute(SchemaExportTask.java:129)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166)
at org.apache.tools.ant.Task.perform(Task.java:317)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:334)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at org.apache.tools.ant.Main.runBuild(Main.java:610)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
The line in the sourcecode is:
model.getKey().createForeignKeyOfClass( model.getOwner().getPersistentClass() );
Tinkering with the sourcecode showed that the problem is that model.getKey() returned 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-10-12 14:21:20
|
Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Sun, 12 Oct 2003 9:20 AM
finally committed this stuff
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-376
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-376
Summary: Hibernate Mapping DTD does not allow meta tags under component
Type: Patch
Status: Closed
Priority: Trivial
Resolution: FIXED
Project: Hibernate2
Fix Fors:
2.1
Versions:
2.0.3
Assignee: Max Rydahl Andersen
Reporter: Hunter Kelly
Created: Wed, 1 Oct 2003 10:54 AM
Updated: Sun, 12 Oct 2003 9:20 AM
Environment: Not applicable
Description:
The <component> element under <class> does not allow meta tags, for
example:
<component name="foo" class="eg.Foo">
<meta attribute="generated-class">eg.FooBase</meta>
<property name="value" type="int"/>
<property name="lastDate" type="timestamp"/>
</component>
However, the hbm2java guy will generate classes for components, so it is necessary to be able to override stuff using the meta tags.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-12 05:48:19
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-394 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-394 Summary: Security : Avoid printing password information in log files Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: John Walshe Created: Sun, 12 Oct 2003 12:47 AM Updated: Sun, 12 Oct 2003 12:47 AM Description: Currently the user password is being written in the log files. For security purposes can it be masked out, ie '?????' ? Atleast two method need to be changed. ------------------------ CLASS: net.sf.hibernate.connectionDriverManagerConnectionProvider METHOD: configure() FROM: log.info( "using driver: " + driverClass + " at URL: " + url ); log.info("connection properties: " + connectionProps); TO: Properties connectionPropsClone = (Properties)connectionProps.clone(); connectionPropsClone.put("password", "?????????"); log.info( "using driver: " + driverClass + " at URL: " + url ); log.info("connection properties: " + connectionPropsClone); ------------------------ CLASS: net.sf.hibernate.impl.SessionFactoryImpl METHOD: () FROM: if ( log.isDebugEnabled() ) log.debug("instantiating session factory with properties: " + properties); TO: if ( log.isDebugEnabled() ) { // Take a copy of the properties and blank out the password field Properties propsClone = (Properties)properties.clone(); propsClone.put("hibernate.connection.password", "?????????"); log.debug("instantiating session factory with properties: " + propsClone); } --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-11 06:53:20
|
The following issue has been updated:
Updater: David Morris (mailto:dmm...@ce...)
Date: Sat, 11 Oct 2003 1:53 AM
Comment:
Unfortunately, anonymous cvs from sourceforge has not been working for a while. This patch was made against my CVS server so may not reflect the latest source. It was built against the beta4 release.
Changes:
Attachment changed to nullprimitive.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-393&page=history
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-393
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-393
Summary: Send meaningful message when null passed to primitive setter(s)
Type: Patch
Status: Unassigned
Priority: Minor
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: David Morris
Created: Sat, 11 Oct 2003 1:51 AM
Updated: Sat, 11 Oct 2003 1:53 AM
Description:
Current exception when passing null value to primitive setter does not indicate the setter that is in error. The attatched patch logs a warning message that identifies primitive value setters receiving null values.
This has been a common error among our developers and a search of the forums indicates others have hit this as well.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
|
From: <leg...@at...> - 2003-10-11 06:51:20
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-393 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-393 Summary: Send meaningful message when null passed to primitive setter(s) Type: Patch Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.1 Assignee: Reporter: David Morris Created: Sat, 11 Oct 2003 1:51 AM Updated: Sat, 11 Oct 2003 1:51 AM Description: Current exception when passing null value to primitive setter does not indicate the setter that is in error. The attatched patch logs a warning message that identifies primitive value setters receiving null values. This has been a common error among our developers and a search of the forums indicates others have hit this as well. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-10 21:29:21
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-14 Here is an overview of the issue: --------------------------------------------------------------------- Key: HBI-14 Summary: hibernate-mapping-2.0.dtd should not contain <?xml version='1.0'... Type: Improvement Status: Unassigned Priority: Minor Project: Hibernate 1.2 Assignee: Reporter: Shane Taylor Created: Fri, 10 Oct 2003 4:29 PM Updated: Fri, 10 Oct 2003 4:29 PM Description: http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd begins with <?xml version='1.0' encoding='utf-8'?>. This should not be in a dtd and causes IE and WebSphere Studio 5.0 to choke on it. WebSphere Studio cannot validate hbm.xml files with DOCTYP refering to http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd. --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
|
From: <leg...@at...> - 2003-10-10 15:47:20
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-392 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-392 Summary: NPE in net.sf.hibernate.cfg.Binder.bindCollectionSecondPass Type: Bug Status: Unassigned Priority: Minor Project: Hibernate2 Components: core Versions: 2.0.3 Assignee: Reporter: Ingo Schildmann Created: Fri, 10 Oct 2003 10:47 AM Updated: Fri, 10 Oct 2003 10:47 AM Description: java.lang.NullPointerException at net.sf.hibernate.cfg.Binder.bindCollectionSecondPass(Binder.java:1076) at net.sf.hibernate.cfg.Binder.bindSetSecondPass(Binder.java:923) at net.sf.hibernate.cfg.Binder$SetSecondPass.secondPass(Binder.java:1187) at net.sf.hibernate.cfg.Binder$SecondPass.doSecondPass(Binder.java:1135) at net.sf.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:497) at net.sf.hibernate.cfg.Configuration.generateDropSchemaScript(Configuration.java:352) at net.sf.hibernate.tool.hbm2ddl.SchemaExport.<init>(SchemaExport.java:51) at net.sf.hibernate.tool.hbm2ddl.SchemaExportTask.getSchemaExport(SchemaExportTask.java:198) at net.sf.hibernate.tool.hbm2ddl.SchemaExportTask.execute(SchemaExportTask.java:129) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) at org.apache.tools.ant.Task.perform(Task.java:317) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:334) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.Project.executeTargets(Project.java:1250) at org.apache.tools.ant.Main.runBuild(Main.java:610) at org.apache.tools.ant.Main.start(Main.java:196) at org.apache.tools.ant.Main.main(Main.java:235) The line in the sourcecode is: model.getKey().createForeignKeyOfClass( model.getOwner().getPersistentClass() ); Tinkering with the sourcecode showed that the problem is that model.getKey() returned 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-10-10 13:32:22
|
Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-391 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-391 Summary: Udated bat files in the tools - defined HIBERNATE_HOME Type: Patch Status: Unassigned Priority: Major Project: Hibernate2 Components: toolset Assignee: Reporter: Mukund Pragasam Created: Fri, 10 Oct 2003 8:31 AM Updated: Fri, 10 Oct 2003 8:31 AM Environment: run the tools (like hbm2java) from any other IDE like JBuilder. Description: In the tools/bin we have class2hbm.bat ddl2hbm.bat hbm2java.bat setenv.bat all the above bat files need to know HIBERNATE_HOME they were using relative path to get it. When I run these tools from JBuilder, they were not working because of the relative path. I extracted hibernate-extensions-2.0.zip in the hibernate home directory. So I had the directory structure like avalon bin build.bat build.xml changelog.txt demo.bat demo.sh doc hibernate2.jar hibernate_logo.gif lgpl.txt lib readme.txt src tools I have modified the files to get HIBERNATE_HOME from the environment variables. For example if "%HIBERNATE_HOME%"=="" goto noHIBERNATEHome call %HIBERNATE_HOME%\tools\bin\setenv.bat java -cp %CP% net.sf.hibernate.tool.class2hbm.MapGenerator %* if not "%HIBERNATE_HOME%"=="" goto end :noHIBERNATEHome echo HIBERNATE_HOME is not set. Please set HIBERNATE_HOME. :end set HIBERNATE_HOME I can send this to the group and they can update this in their copy. I can send all the bat files with similar updates. I am not sure how this works. Will this be Assigned To me? or Do I need to send the modified bat files in a mail...? --------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira |
93 messages has been excluded from this view by a project administrator.
