[jboss-user] [JNDI and Naming] - Why JBoss enforces java:/ java:boss/ naming and how to override it in the jboss-ejb3.xml?

Mark Ashworth do-not-reply at jboss.com
Fri Jan 13 09:15:24 EST 2012

Mark Ashworth [https://community.jboss.org/people/mpashworth] created the discussion

"Why JBoss enforces java:/ java:boss/ naming and how to override it in the jboss-ejb3.xml?"

To view the discussion, visit: https://community.jboss.org/message/646699#646699

Good Day,

I am busy writing an application that uses JPA and JMS and noticed during the setup process of JBoss 7.1 CR1b (but it possibly relates to JBoss 7.x) that JBoss enforces the java:/ and java:jboss/ names for resources. I updated the application references and it worked but the problem is that I would like the application to be deployable to Glassfish, JBoss and Weblogic.

 Can someone point me to an example or the jboss-ejb3.xml schema so that I can use it override the annotations on the class files. And just maybe as an additional note, does JBoss support a deployment.xml file similar to Weblogic that provides the deployment specific overrides?

Your assistance is greatly appreciated.

Mark P Ashworth
 http://mpashworth.wordpress.com http://mpashworth.wordpress.com

Reply to this message by going to Community

Start a new discussion in JNDI and Naming at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20120113/304fdf9e/attachment.html 

More information about the jboss-user mailing list