Unable to override JNDI name for session bean

[keigwin]

I'm using JBossAS 5.1.0 and have just upgraded the Eclipse projects for an existing application to support EJB3. I then converted one of the session beans in the app to an EJB3-style declaration. I've been able to successfully call this bean if I use JBoss' default JNDI name for the bean.

Now I need to override the JNDI name and have had no luck doing this. The mappedName attribute in the @Stateless annotation seems to have no effect on the name the bean is bound to. For example, with the bean declared this way:

@Stateless(mappedName="com.sellcore.service.GeographyService")
public class GeographyService implements GeographyServiceLocal
{

the JBoss management console shows it is still bound to the default name:

+- UnitTestsEAR (class: org.jnp.interfaces.NamingContext)
 | +- GeographyService (class: org.jnp.interfaces.NamingContext)
 | | +- local-com.sellcore.facade.common.GeographyServiceLocal (class: Proxy for: com.sellcore.facade.common.GeographyServiceLocal)
 | | +- local (class: Proxy for: com.sellcore.facade.common.GeographyServiceLocal)

where UnitTestsEAR is the EAR containing the bean and its client WAR.

The appserver logs show that the new name is found by JBoss:

15:12:13,249 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=UnitTestsEAR.ear,jar=SellCoreService.jar,name=PrintApplication,service=EJB3) to KernelDeployment of: SellCoreService.jar
15:12:13,249 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=UnitTestsEAR.ear,jar=SellCoreService.jar,name=GeographyService,service=EJB3
15:12:13,249 INFO [JBossASKernel] with dependencies:
15:12:13,249 INFO [JBossASKernel] and demands:
15:12:13,249 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
15:12:13,249 INFO [JBossASKernel] and supplies:
15:12:13,249 INFO [JBossASKernel] jndi:UnitTestsEAR/GeographyService/local-com.sellcore.facade.common.GeographyServiceLocal
15:12:13,249 INFO [JBossASKernel] jndi:UnitTestsEAR/GeographyService/local
15:12:13,249 INFO [JBossASKernel] jndi:com.sellcore.service.GeographyService
15:12:13,249 INFO [JBossASKernel] Class:com.sellcore.facade.common.GeographyServiceLocal

But the value I specified as the mappedName is not used at binding time, as shown later in the log:

15:12:13,937 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=UnitTestsEAR.ear,jar=SellCoreService.jar,name=GeographyService,service=EJB3
15:12:13,937 INFO [EJBContainer] STARTED EJB: com.sellcore.service.common.GeographyService ejbName: GeographyService
15:12:13,952 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

 UnitTestsEAR/GeographyService/local - EJB3.x Default Local Business Interface
 UnitTestsEAR/GeographyService/local-com.sellcore.facade.common.GeographyServiceLocal - EJB3.x Local Business Interface

I know I'm probably doing something really ignorant, but I can't figure out what. I'd really appreciate any assistance!

Thanks,

K-

[jaikiran]

The mappedName is vendor specific and JBoss does not use it to for JNDI bindings. What you need is here http://www.jboss.org/file-access/default/members/jbossejb3/freezone/docs/tutorial/1.0.7/html/JNDI_Bindings.html

[keigwin]

Thanks for the quick reply! I appreciate your help.

[keigwin]

It looks as if I'm going to need to override the JNDI names for my existing EJB2 beans as well. It seems that JBoss is ignoring the <jndi-name> entries in jboss.xml, and is giving default names to all of the old-style beans.

The @LocalBinding annotation doesn't work in this case.

Any help with the right approach will be much appreciated!

K-

[jaikiran]

It looks as if I'm going to need to override the JNDI names for my existing EJB2 beans as well. It seems that JBoss is ignoring the <jndi-name> entries in jboss.xml, and is giving default names to all of the old-style beans.

Please post relevant configuration and code from ejb-jar.xml, jboss.xml and the ejb impl. Are you trying to set the local jndi name? Then you should use local-jndi-name in the jboss.xml. Also take a look at the JNDI tree to see what exact jndi names are being used to bind your EJBs http://www.jboss.org/community/wiki/DisplayTheJDNITreeWithTheJMXConsole

[keigwin]

This is an existing, working EJB2.1 application. I added an EJB3-style bean and JBoss started ignoring the JNDI names specified using the <local-jndi-name> tag in jboss.xml.

I was able to "fix" the problem by removing the EJB3 bean and reverting my ejb-jar.xml to it's earlier state.

Does this mean that EJB2 and EJB3 beans cannot coexist in the same ejb-jar?

[tflora]

Did this ever get resolved? I am having similar issues.

1) I have EJB2.x beans.

2) I have converted them to EJB3 by adding the EJB3 Schema information to the ejb-jar.xml file. (I need to use interceptors).

3) The JBoss.xml jndi-name is ignored and the home interface is bound to the EarName/EJBName/home location in the global JNDI.

4) If I leave the ejb-jar.xml at the 2.1 version schema the simple jndi-name is used and my app works file but once I use the ejb 3 file header for the ejb-jar.xml file jndi is no longer valid.

How do you fix this? I have 1000's of lines of code that reference our EJB's in the original locations. Also we publish an external API for our customers to use and they likewise will have much code that expects the home interface for these EJB's to be bound in their original location.

Please help!

Thanks,

Todd Flora

Senior Developer

Power Costs Inc.

[tflora]

OK, So found the problem here. Not really a problem but just a feature that I was unaware of.

Just in case someone else finds this post in search of the solution. I found it here:

http://community.jboss.org/wiki/DevJNDIBinding

home-jndi-name did the trick for me.

Regards,

Todd Flora

Senior Developer

Power Costs, Inc.

[gthorburn]

We also encounted a similar problem when migrating EJB2.1 to EJB3.0 (and WSAD 5.1.2 -> Eclipse Galileo). Addition of the JBoss.xml to the  projects META-INF folder was our solution.  Our app only uses local business interfaces, and the JBoss.xml looks like the following:

<?xml version="1.0" encoding="UTF-8" ?>

<jboss>
    <enterprise-beans>
        <session>
            <ejb-name>TestBean</ejb-name>
            <local-jndi-name>ejb/TestBean</local-jndi-name>
        </session>
    </enterprise-beans>
</jboss>

The <local-jndi-name> can then be used in the InitialContext lookup, without having to use the default "<AppName>/BeanName" format (JBoss 5.1.0).

Regards,

Greg

[skajotde]

My post http://skajotde.wordpress.com/2010/10/21/tdd-ejb21-with-arquillian-and-jboss/ uses mapping for jndi EJB 2.1. There are also source codes.