Re: No bean could be found in the registry for JNDI Look up using EJB Component

Pleasure. Have fun !!! Dwiti -- View this message in context: http://camel.465427.n5.nabble.com/No-bean-could-be-found-in-the-registry-for-JNDI-Look-up-using-EJB-Component-tp5749335p5753901.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: No bean could be found in the registry for JNDI Look up using EJB Component

Hi, I'm currently facing the same problem that you describes. Did you solve this issue? Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/No-bean-could-be-found-in-the-registry-for-JNDI-Look-up-using-EJB-Component-tp5749335p5753882.html Sent from the Camel - Users

Re: No bean could be found in the registry for JNDI Look up using EJB Component

Yes,The issue is resolved.Here is the action points might be helpful for you.-- Stubs should be present in your camel code(EJB remote interface)-- EJB component sd be registered with correct initial contextLet me know if this does not work and share your trace and code.Thanks, Dwiti -- View

Re: No bean could be found in the registry for JNDI Look up using EJB Component

Hi and thanks for the quick response! Now it's working ok... as you point, the problem was that the ejb remote interfaces were not present in camel app. Thanks a lot! -- View this message in context:

No bean could be found in the registry for JNDI Look up using EJB Component

Hi, My stateless session bean is deployed in JBOSS eap 6 and I can invoke it using standalone java client. But while integrating it with camel route i am getting below exception. Stacktrace