Java – Remote lookup using @ejb annotation

ejbjava

I have 2 servers instances of Jboss 5, each of which is deployed with two EAR's. Say Client.Ear and Server.Ear.
Server Ear expose some ejb's. I want to inject this to ClientEar via annotation. Using JNDI lookup i did it fine and it works. But using annotation i always get javax.naming.NamingException.
However when injecting session beans accross deployment artifacts the global JNDI name has to be used for injection and i used that also like
@EJB(mappedName ="java:global/Server/component/ApplicationService!com.test.server.ApplicationServiceInterface")

But it seems like I am not providing the provider_url of the remote server to bound it to the client ear instance.
How could i configure jndi properties, ie provider_url, initial context properites with the annotation @ EJB?

Best Answer

I found a forum post that answers your question: https://community.jboss.org/thread/228789

In it he refers to https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+server+instance

And to accomplish the jndi lookup with the @EJB annotaion he uses

@EJB(lookup = "ejb:earname/modulename/BeanClass!fully.qualified.RemoteInterface")
private RemoteInterface bean;

Related Solutions

Problem doing jndi lookup for EJB

Try:

return ( CodesService )ctx.lookup( "java:global/gss-ea/gss-ejb/CodesBean" );

Note: no "/" before "global".

Java – @Inject, @EJB, @Local, @Remote, @LocalBean, etc… : confused

As you can see, I have declared the annotation "@Local" on the service implementation without defining the local interface. Is it correct?

With EJB 3.1, the requirement for local interfaces was dropped. No need to write them unless you explicitly need them.

What is the best way to inject one EJB into another one?

Couple of things to write here:

With Java EE 6, Java Enterprise has changed. A new JSR defines a so-called managed bean (don't confuse with JSF managed beans) as a sort of minimum component that can still benefit from the container in terms of dependency injection and lifecycle management. This means: If you have a component and "just" want to use DI and let the container control its lifecycle, you do not need to use EJBs for it. You'll end up using EJBs if - and only if - you explicitly need EJB functionality like transaction handling, pooling, passivation and clustering.

This makes the answer to your question come in three parts:

Use @Inject over @EJB, the concept of CDI (a) works for all managed beans (this includes EJBs) and (b) is stateful and therefore far superior over pure @EJB DI
Are you sure that you need EJBs for your components?
It's definitely worthwhile to have a look at the CDI documentation

Best Answer

Related Solutions

Problem doing jndi lookup for EJB

Java – @Inject, @EJB, @Local, @Remote, @LocalBean, etc… : confused

Related Topic