Message:
The following issue has been closed.
Resolver: Gavin King
Date: Fri, 5 Sep 2003 4:12 AM
The test code works fine against my current CVS snapshot. The problem may have already been fixed.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-311
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-311
Summary: key-many-to-one in composite-id causes MappingException
Type: Bug
Status: Closed
Priority: Major
Resolution: CANNOT REPRODUCE
Project: Hibernate2
Components:
core
Versions:
2.1 beta 2
Assignee:
Reporter: Greg Barton
Created: Fri, 5 Sep 2003 12:26 AM
Updated: Fri, 5 Sep 2003 4:12 AM
Environment: mapping
Description:
Placing a key-many-to-one element in a composite-id element can cause a MappingException to be thrown when creating a SessionFactory.
NOTE:
See attached tar. Run the and script for a demonstration. The only jar I included was the hibernate-tools.jar, as I compiled it from the latest CVS snapshot.
Versions used:
Hibernate 2.1 beta 2
Hibernate tools from CVS snapshot 2003-09-04
I was able to find one situation where the MappingException was NOT thrown. If you run the com.foo.bar.data.Demonstration class from the command line and do NOT put log4j.jar in the classpath, the SessionFactory is created successfully. (Doing this while running from the Ant script STILL results in a MappingException.)
---------------------------------------------------------------------
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
|
