I'm afraid this is not a 'claning-up' issue because I'm talking about portability on PHYSICAL artefacts. You should consider I'm just describing evidence-based facts. Lets go for some scientific experience :
1) Build the wars with Maven from the git ub repository. 2) Put them in JBoss 7.1 => OK 3) Put them in Glassfish 3.1 => OK 4) Put them in Weblogic 12c => OK OK means that Remote Interface is casted into the regular interface and ui.war is able to communicate with engine.war. UI is printing a regular message coming from the engine in any of those JEE6 AS. I think there would be no problem on Websphere 8.5, not tested yet. 5) NOW put them (same PHYSICAL aretefacts as 1-2-3-4) in TomEE -> *KO* *KO* means that there is a ClassCast Exception, because OpenEJB is not able to rekognise the remote interface that the proxy must cast. UI is displaying the exception on TomEE. This is only science / evidence-based experimentation. Please, just reconsider you last post. Now my question is the following : if it is 'already working' how would you explain these facts ? Actually, my conclusion is that remote interfaces on OpenEJB are not working like a JEE6 'standard' AS. Neither on TomEE 15.2 OR 16.0 My code is minimalistic. So, maybe there is something I should add in the code that is more specific on TomEE ? Like some stuff within ejb-jar.xml or web.xml // <ejb-ref> ? But I would tell you that I saw nothing in TomEE documentation in that sense. Kind Regards. -- View this message in context: http://openejb.979440.n4.nabble.com/Classcast-execption-on-proxy-when-looking-up-remote-interface-tp4662060p4662409.html Sent from the OpenEJB User mailing list archive at Nabble.com.
