I applied your patch and verified it with the supplied jar. I believe
the problem is caused by the cmp field personId being mapped to the
cmr field person.
Can you verify that the patch fixes your problem?
BTW in the openejb-jar.xml file you put the following:
<entity>
<ejb-name>Person</ejb-name>
<local-jndi-name>java:comp/env/ejb/Person</local-jndi-name>
which is not a valid global jndi name.
-dain
On Mar 2, 2008, at 1:02 PM, Jonathan Gallimore wrote:
Hi
I posted this: http://www.nabble.com/ClassFormatError-when-deploying-an-EJB2-CMP-bean-with-a-many-to-one-relationship-td15148184.html
on the mailing list a little while ago, and also added Jira issue
750.
Basically I was running into some trouble deploying a CMP entity
bean with a many to one relationship, and one of classes generated
by the deployment process had duplicate methods in it.
I'm not sure if I'm doing something wrong in my app, or whether its
a bug - if its a bug I think it would be nice to have it fixed in
the final release of 3.0. I attached a potential fix to the Jira
(its only a three liner).
Cheers
Jon
David Blevins wrote:
So it seems like we've gotten the feedback we're going to get on
the 3.0-beta-2. We just have a handful of issues left to clean up:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310530&fixfor=12312805
I'd say once we get these completed, we should cut the big 3.0 final.
Anything you'd like to see get in not in that list? Thoughts?
-David
