Thanks for the quick (and clever) reply ! It "looks like" what you are describing, but that code is currently running well on others JEE6 app servers. So I wonder either my code is not absolutely JEE6 compliant or if this is a bug of TomEE / OpenEjb.
OK this is more precision about that issue. I have 2 wars running within the same AS / TomEE 1.5.1 with a common jar : project-bind.jar -> remote interface project-core.war => dependancy on project-bind -> Stateless impl project-ui.war => dependancy on project-bind -> client implementation project UI is providing a JSP and connects to the project-core.war My goal is to provide a full portable EJB poc on different AS. And I'm really suprised that the more difficult is deploying on TomEE that should be a reference implementation ?! Best Regards. -- View this message in context: http://openejb.979440.n4.nabble.com/Classcast-execption-on-proxy-when-looking-up-remote-interface-tp4662060p4662063.html Sent from the OpenEJB User mailing list archive at Nabble.com.
