I had to make similar changes to get EJBs working when migrating from Websphere to TomEE. I am not an EJB expert, but I think recent updates of the spec are trying to make the namespace universal to avoid vendor-specific namespaces.
Also, TomEE's system.properties has a "openejb.jndiname.format" property that allows you to configure the format of the name space. In some cases, I was able to use this setting to make TomEE's JNDI namespace similar to Websphere's. I set it to: openejb.jndiname.format=ejb/{interfaceClass.simpleName} -----Original Message----- From: luca-vercelli [mailto:luca.verce...@alkeinformatica.com] Sent: Tuesday, September 27, 2016 10:00 AM To: users@tomee.apache.org Subject: Re: Migrating EJB from Jboss to TomEE After 2 weeks, I can finally work on this again. Apparently, the Jndi names are completely different between JBoss and TomEE. For example, where in JBoss I had: "LogCaricamentoService/local" and "queue/massiveLoading/load" and in TomEE I had to write: "java:openejb/Deployment/LogCaricamentoService/it.packagename.LogCaricamentoServiceLocal!Local" and "java:openejb/Resource/queue/massiveLoading/load" Is this normal? Or am I missing something? Thank you. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Migrating-EJB-from-Jboss-to-TomEE-tp4680044p4680203.html Sent from the TomEE Users mailing list archive at Nabble.com.