"[EMAIL PROTECTED]" wrote : The war should not have the interfaces when using the default war first class loading mode as this results in inconsistent types. |
That finally solved the problem! For the sake of usablity, this hint should be in the error message when getting a ClassCastException on EJB3 lookup, when classnames are identical and classloaders differ. Especially because in the old ways of J2EE, the EJB-interfaces have to be present in the war - now they are not allowed to. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936578#3936578 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936578 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
