Ok, hacked a bit on it (https://issues.apache.org/jira/browse/TOMEE-892) but with current code it should have worked if you ensure the engine starts before the ui (not nice but that's just a workaround). It can be achieve using tomee.xml <Deployments> or server.xml <Context>.
That said that's maybe not really your issue. IMO your issue was you put the api jar (bind with your vocabulary) in both webapps so each webapp uses it own copy. Just put your bing jar in tomee/lib AND remove it from webapps and it works. *Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/4/8 skay <[email protected]> > Hi, > > I just pushed on github the minimal code so that you can reproduce / > investigate further. > > https://github.com/skay2k/ejblookup > > Maven project with 3 modules / 2 artefacts > > ejblookup-engine.war (with stateless) > ejblookup-ui.war (with interface lookup) > > you'll notice that the Remote interface annotation is set only on the > stateless bean / not on the interface itself. This is OK according the > specs > and running on other targeted AS. You may change this / I didn't find any > solution with TomEE playing with annotations. > > On the ui side, I tryed diffrent solution / with / without InitialContext > properties settings. Just calling new InitialContext() is OK for the other > target AS / nothing worked for me with TomEE. > > Thank you for your time ! > > > Thank you very much for your support ! > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Classcast-execption-on-proxy-when-looking-up-remote-interface-tp4662060p4662119.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
