This is working for a simple testcase. Two jboss servers running
the minimal config are able to come up with the JNDI naming
service running on ports 1098 and 1099 using this type of config
in the conf/jboss-service.xml descriptor:
<server>
<mbean code="org.jboss.services.binding.ServiceBindingManager"
name="jboss.system:service=ServiceBindingManager">
<attribute name="ServerName">jboss1</attribute>
<attribute name="StoreURL">file:/etc/jboss-bindings.xml</attribute>
<attribute
name="StoreFactoryClassName">org.jboss.services.binding.XMLServicesStoreFact
ory</attribute>
</mbean>
...
</server>
The sample jboss-bindings.xml config shared by the two servers looks like:
bin 541>cat /etc/jboss-bindings.xml
<!DOCTYPE service-bindings>
<service-bindings>
<server name="jboss0">
<service-config name="jboss:service=Naming"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
>
<delegate-config portName="Port" hostName="BindAddress"/>
<binding name="default" host="" port="1098" />
</service-config>
</server>
<server name="jboss1">
<service-config name="jboss:service=Naming"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
>
<delegate-config portName="Port" hostName="BindAddress"/>
<binding port="1099" />
</service-config>
</server>
</service-bindings>
The AttributeMappingDelegate class takes the host and port specified by the
binding element and invokes setAttribute using the attribute names given
by hostName and portName.
I'll be testing the mappings for other services tomorrow.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
