jboss.xml seems to be ignored in EJB 3?

[platinumdragon]

Hello again,

I am attempting to use EJB 3 (AS 4.0.3 RC1) on Windows XP Pro SP2.

I have a working sample stateful EJB and can access it through its remote interface classname in JNDI, as is the default behavior in EJB 3.

But, I would like to access it through a more generic name. I understand that jboss.xml allows you to override the default behavior, thus I have:

<jboss>
 <enterprise-beans>
 <session>
 <ejb-name>DefaultProxy</ejb-name>
 <jndi-name>com/mycompany/proxy/default</jndi-name>
 </session>
 </enterprise-beans>
</jboss>

and have placed this in the ./META-INF directory.

In the DefaultProxy, I have the annotation

@Stateful(name="DefaultProxy")

I am assuming this is how the entry in jboss.xml gets linked to the EJB.

And all of this gets packaged up in a proxy.ejb3 file and deployed. The problem is, that it still gets deployed under the remote interface name.

It seems to me that the jboss.xml is either being ignored, or I am not doing what is necessary to link the two of them. I've been through all of the tutorials I can find, but this seems to be a fuzzy spot.

Could someone please enlighten me?

Thanks,
Mike

[platinumdragon]

It's definitely being ignored. The logs are producing:

09:02:49,646 INFO [ProxyDeployer] no declared remote bindings
09:02:49,646 INFO [ProxyDeployer] there is remote interfaces
09:02:49,646 INFO [ProxyDeployer] default remote binding has jndiName of com.mycompany.util.Proxy

So I'm left with the question: is this a bug or user error?

[platinumdragon]

Hmm.. Disappointing

[darranl]

Can you execute the command 'jar -tf proxy.ejb3' an post the output here.

http://docs.jboss.org/ejb3/tutorial/index.html

The tutorials above should confirm for you how JNDI bindings can be set.

[platinumdragon]

Thank you Darran,

proxy.ejb3:

META-INF/
META-INF/MANIFEST.MF
com/
com/mycompany/
com/mycompany/proxy/
META-INF/jboss.xml
com/mycompany/proxy/DefaultProxy.class

The actual proxy interface is in a jar next to proxy.ejb3, called util.jar:

META-INF/
META-INF/MANIFEST.MF
com/
com/mycompany/
com/mycompany/util/
com/mycompany/util/Proxy.class

where Proxy is a simple interface with the @Remote annotation.

I've been through the tutorial, which is where I got the jboss.xml from. The only other thing I see that would possibly apply is the "JNDI Bindings" section which would unfortunately tie the code itself to JBoss (not that I have anything against JBoss). If possible, I would like to keep anything container-specific in the configuration files.

Thanks again for your response,
Mike