Invalid RmiPort binding for HAJNDI service

The port bindings for HAJNDI service in sample server-bindings.xml is invalid.

As written: <service-config name="jboss:service=HAJNDI"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
>
<delegate-config portName="RmiPort"/>
<binding port="1198"/>
</service-config>

<service-config name="jboss:service=HAJNDI"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
>
<delegate-config portName="Port"/>
<binding port="1200"/>
</service-config>

it contains a couple of problems.
The service-config is present twice for the same service and the first one is ignored, so RmiPort is not rebinded, then, the port number for RmiPort is 1198 which conflicts with the same attribute for jboss:service=Naming.

The binding should be:

<service-config name="jboss:service=HAJNDI"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
>
<delegate-config portName="Port">
<attribute name="RmiPort">1201</attribute>
</delegate-config>
<binding port="1200"/>
</service-config>

The problem is evidenced in this release because the RmiPort for HAJNDI, into cluster-service.xml, changed from 0 to 1101 and now if you start a couple of instances in the same machine they conflict on that port.