Message:
The following issue has been closed.
Resolver: Gavin King
Date: Wed, 10 Dec 2003 5:59 AM
Don't use interface proxies if you have this. Use the actual concrete classes as the proxy class.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-537
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-537
Summary: Proxy Problem with overloaded functions
Type: Bug
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Versions:
2.0.3
Assignee: Gavin King
Reporter: Panagiotis Louridas
Created: Wed, 10 Dec 2003 5:50 AM
Updated: Wed, 10 Dec 2003 5:59 AM
Environment: linux, Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28), hibernate 2.0.3, postgres.
Description:
Suppose we have class A and two subclasses A<-B, A<-C. Suppose now that B has methods Foo getFoo() and void setFoo(Foo), while C has methods Bar getFoo() and void setFoo(Bar).
I get strange proxy behaviour when working with objects of classes A, B, C. Specifically, when querying on B, C and then on A, I get
SEVERE: CGLIB Enhancement failed
java.lang.IllegalArgumentException: Can't implement:
InterestPayment
and
TaxPayment
(where InterestPayment = B and TaxPayment = C).
Everything works fine when querying on A and then on B and C, though.
---------------------------------------------------------------------
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
|
