This content has been marked as final.
Show 5 replies
-
1. Re: HAJNDI access of NamingContext.localServer
brian.stansberry Oct 1, 2008 3:23 AM (in response to starksm64)Sounds good.
For the related TODO in the HAJNDI code we really should be injecting the Naming instance. When I integrate the next jnpserver version I will be switching the naming service configuration to be an mc -beans.xml deployment.
When you change the naming service config to -beans.xml, do you intend to add the injection into DetachedHANamingService, or shall I add a JIRA to handle that myself?
I'll also be converting the hajndi-service.xml back to a -beans.xml for GA, so it's convenient enough for me to add the injection when I do that. -
2. Re: HAJNDI access of NamingContext.localServer
starksm64 Oct 2, 2008 10:24 AM (in response to starksm64)Create the jira and someone will get to it. I'll most likely get to it since I'll need to get the all config running for the smoke/naming tests in jbossas.
-
4. Re: HAJNDI access of NamingContext.localServer
brian.stansberry Oct 21, 2008 4:52 PM (in response to starksm64)Scott, I'd done JBAS-6023 (inject Naming into HA-JNDI) but it got reverted. I'm about to reapply it, but since your extract of the naming service from conf/jboss-service.xml isn't being reapplied, I'm now doing the injection from a legacy mbean rather than a pojo:
<property name="localNamingInstance"><inject bean="jboss:service=NamingBeanImpl" property="namingInstance"/></property>
If you ever redo the pojoization of the naming service, we'll need to change that to:<property name="localNamingInstance"><inject bean="LocalNamingBean" property="namingInstance"/></property>
in the following files:
cluster/src/etc/hajndi-jboss-beans.xml
testsuite/src/resources/cluster/ejb2/passexp/partition-passexp-jboss-beans.xml
testsuite/src/resources/cluster/partition/partition-restart-jboss-beans.xml -
5. Re: HAJNDI access of NamingContext.localServer
starksm64 Oct 21, 2008 6:04 PM (in response to starksm64)Ok.