The AdminConsole, in its tab ServiceBindingManager, does not seem to correctly reflect settings present in the ServiceBindingManager's configuratioin files.

For example, the service jboss:service=HAJNDI needs to specify both the hostName and port attributes in its ServiceBindingMetadata entry in server/all/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml file:

<bean class="org.jboss.services.binding.ServiceBindingMetadata">
<property name="serviceName">jboss:service=HAJNDI</property>
<property name="bindingName">AutoDiscovery</property>
<property name="hostName">${jboss.partition.udpGroup:230.0.0.4}</property>
<property name="port">1102</property>
<property name="description">Multicast socket on which HA-JNDI listens for auto-discovery requests from clients</property>
<!-- This address should not be changed between different
binding sets; all nodes need to listen on the same
multicast address -->
<property name="fixedHostName">true</property>
<!-- This port should not be changed between different
binding sets; all nodes need to listen on the same port -->
<property name="fixedPort">true</property>
</bean>

but these are appearing as "not set" in the AdminConsole (see the attached image).

Furthermore, most of the metadata entries should pick up the default host specification from the BindingServiceSet, and i'm wondering if these should also not appear here.