JBoss ignores metadata supplied in a JAX-RPC Mapping DD. Part 1.

In using the WS subsystem of JBoss, I observed that it ignores a fair amount of metadata supplied in a JAX-RPC Mapping DD. In particular I observed the following:

java-xml-type-mapping.

Jboss ignores the 'xml-element-name' element on the assumption that its value is the same as that of the 'java-variable-name' element. E.g. with the following info in the typemapping DD, JBoss will fail to deserialize incoming requests if the envelope contains 'collectionElements' and not 'typedElements':
Code:
<java-type>pack.JavaType</java-type>
<root-type-qname xmlns:typeNS="http://namesp">typeNS:XMLType</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>typedElements</java-variable-name>
<xml-element-name>collectionElements</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>

class JavaType {
private Double array[];
Double[] getTypedElements()

{ return array; }

void setTypedElements(Double s[])

{ array = s; }

}

Note: JBoss disregards information provided by the 'xml-element-name' element in favour of JavaBean introspection on the JavaType bean.

Needless to say that this behaviour is not conformant with the "Web Services for J2EE, Version 1.1" specification. Setting severity to 'Critical'.