AS 6 & JNDI bindings: overriding the module name

[vincent_aumont]

Hi,

I have this bean:

{code}
@stateless
public class MyBean{
[...]
}
{code}

packaged in a jar that it itself packaged in a war (mywar-1.0.0-SNAPSHOT.war).

When I deploy this war, AS binds the bean to java:module/MyBean and java:global/myapp-1.0.0-SNAPSHOT/MyBean.

So far so good, but I'd like to map the bean in the global scope as java:global/myapp/MyBean

I thought that the spec-compliant way to do this was to set the application's root context.

So, My jboss-web.xml looks like this:

{code}
<jboss-web>
  <context-root>/myapp</context-root>
</jboss-web>
{code}

But it does not work, the bean is still bound to java:global/myapp-1.0.0-SNAPSHOT/MyBean.

(it works on Glassfish 3.1, though)

What is the proper way to change the module name in the java:global/<module-name>/<bean name> jndi name?

Thanks,

Vincent

[genman]

I think context-root refers to the directory web pages are served from.

JBoss does have a way to relocate: http://docs.jboss.org/ejb3/app-server/tutorial/jndibinding/jndi.html

Also look at: http://community.jboss.org/thread/120550

[vincent_aumont]

Thanks Elias.

The pb with LocalBinding it's that it's not portable. We're using GF Embedded in our unit tests.

I'm not sure the org.jboss.naming.NamingAlias can alias the jndi name in the global scope.

There must be an easier way. Could ejb-jar.xml be the solution?

[jaikiran]

When I deploy this war, AS binds the bean to java:module/MyBean and java:global/myapp-1.0.0-SNAPSHOT/MyBean.

So far so good, but I'd like to map the bean in the global scope as java:global/myapp/MyBean

That syntax is mandated by the EJB3.1 spec. The myapp-1.0.0-SNAPSHOT is the "module" name and it can be overriden from within the module deployment descriptor. In this case it is the ejb-jar.xml. So something like this in the ejb-jar.xml should do it:

<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"
         version="3.1">
    <module-name>myapp</module-name>

</ejb-jar>

[vincent_aumont]

I tried this solution, but then I hit this bug:

https://issues.jboss.org/browse/JBAS-8846 ("JEE 6 application gives errors when deploying having ejb-jar.xml contain module name tag")

and all  my EJB's fail to deploy:

{code}
Deployment "jboss.ejb3:application=webapp-1.0-SNAPSHOT,module=webapp-1.0-SNAPSHOT,component=DummyEJB,service=EjbEncFactory" is missing the following dependencies:
    Dependency "jboss.naming:application=webapp-1.0-SNAPSHOT,component=DummyEJB,module=webapp-1.0-SNAPSHOT" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:application=webapp-1.0-SNAPSHOT,component=DummyEJB,module=webapp-1.0-SNAPSHOT' **")
{code}

[genman]

A lot of the AS 6 issues aren't going to be fixed by Redhat. Some have been closed due to lack of interest.

You *can* create patches for things like this. Check out the source and get hacking.