I meant that the ejb-class you specify in ejb-jar.xml might extend some other class, inherit its abstract setters and getters that you declare as cmp and cmr fields in the ejb-jar.xml and at the same time override these same inherited abstract setters and getters. Earlier we mapped CMP/CMR field and ejbSelect invocation handlers (more accurately bridges) to Method objects (one to one). In the iheritance case like above, doing casting tricks in some JVMs it could occur that we invoked a getter or setter defined in the super class that was not mapped to its bridge resulting in the mentioned error.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833647#3833647 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833647 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
