I have the same question/problem. It looks like jboss has switched off the catalina naming service and overridden naming configuration in server.xml and context.xml. It's easy enough to do these in web.xml and jboss-web.xml but since both of these are deployed with the WAR file, it doesn't look like there is any simple way to bind names into the java:comp/env context (ENC) using server configuration. If there is, I've missed it.
I've done a work around using JNDIBindingServiceMgr, but these use global naming and component isolation to some extent. I don't quite understand why the GlobalNamingResources/Resource tags in server.xml and ResourceLink tag in context.xml would be turned off without providing some equivalent functionality.
Whoops -- my 2nd pg 1st sentence should read "I've done a work around using JNDIBindingServiceMgr, but this uses global naming and **breaks** component isolation to some extent.
JBoss Day 1 and I'm trying to solve this same problem.
bwtaylor, do you have the MBean definition you used to get the JNDIBindingServiceMgr to put a Jackrabbit repository in JNDI? I'm not really au fait with JBossXB - do I need to be?
Your help would really be appreciated - I'm think in at the deep end here.
Thanks in advance
There was a bug in Jackrabbit 1.0 that prevented using the org.apache.jackrabbit.core.jndi.RegistryHelper to properly register the repository with a JNDI server. This should be fixed in in Jackrabbit 1.0.1.
So, instead of trying to register the repository using GlobalNamingResources, you can just call RegistryHelper.registerRepository method.
You can have a look at the Jackrabbit bug here: