JBWS-1260 - Unwrapping and complex types with attributes.

[dlofthouse]

I am currently working on JBWS-1260, I have a set of 27 different WSDLs that I have put through wscompile and I am then putting through wstools to compare the generated artifacts.

If the complex type is defined as having a sequence and attribtes: -

 <complexType name='Person'>
 <sequence>
 <element name='surname' nillable='true' type='string'/>
 </sequence>
 <attribute name='postcode' type='string'/>
 </complexType>

wscompile creates the following SEI method: -

public org.jboss.test.ws.jbws1260.TelephoneNumber lookup(java.lang.String postcode, java.lang.String surname) throws java.rmi.RemoteException;

However according to the JAX-RPC 1.1 specification to qualify as using the "wrapper" style the third requirement says: -

such an element (a wrapper) must be of a complex type defined using the
xsd:sequence compositor and containing only elements declarations.

JAX-WS 2.0 expands on this to explicitly prevent the use of attributes.

How should we interpret this? Is wscompile unwrapping the complex type incorrectly or is this how it should be unwrapped?

[dlofthouse]

Actually just found this from the examples in the JAX-RPC 1.1 spec: -

The JAX-RPC specification does not specify a standard Java mapping for a
xsd:complexType with the xsd:anyAttribute. So the message part in the
DoAnotherExample message is mapped as a SOAPElement.

[dlofthouse]

Forget that, the paragraph refers to anyAttribute not attribute.

[jason.greene]

wscompile is incorrect, and it is actually wrong in many areas like this. A complex type should only be unwrapped if there are no attributes. The reason is lack of order which is essential to determining a correct method signature.

On this topic, we have a bug where array types are unwrapped if there are attributes.


http://jira.jboss.com/jira/browse/JBWS-1189