Custom JNDI bindings without bean interface

akoledzhikov Nov 7, 2011 5:17 AM

Is there a way to have stateless ejb bound to custom jndi name (since the default names are quite verbose and somewhat confusing) without providing a local/remote interface. Currently, I'm doing it like this:

@Stateless

@EJB(name = "java:global/ejb/AlienEntityHome", beanInterface = AlienEntityHomeInterface.class)

@SuppressWarnings("unchecked")

public class AlienEntityHome implements AlienEntityHomeInterface

but, since EJB 3.1 specification says that interfaces are no longer required, I thought it should be possible to ommit it. Unfrotunately, when I try to skip the interface, I get:

org.jboss.as.server.deployment.DeploymentUnitProcessingException: @EJB attribute 'beanInterface' is required fo class level annotations.

Any ideas how can I have custom jndi name and take advantage of the new spec at the same time? Thanks in advance

1. Re: Custom JNDI bindings without bean interface

wolfc Nov 7, 2011 5:50 AM (in response to akoledzhikov)
Can you elaborate on the verbosity of the default names?

beanInterface is mandatory, but can contain the bean class for no-interface views.
@EJB(name = "java:global/ejb/AlienEntityHome", beanInterface = AlienEntityHome.class) @LocalBean // needed if implementing any interfaces
Actions
2. Re: Custom JNDI bindings without bean interface

akoledzhikov Nov 8, 2011 8:01 AM (in response to wolfc)

Well, the new portable jndi name syntax is quite long - .../<archive-name>/<module-name>/BeanClassName, and may confuse someone who does not know what's in those archives. /aliens/AlienEntityHome is much clearer and developer-friendly in my opinion.
Using the class as a beanInterface worked for me, thanks!
Actions
3. Re: Custom JNDI bindings without bean interface

wolfc Nov 8, 2011 9:55 AM (in response to akoledzhikov)

Kudos for finding such a solution.
Actions

Go to original post