Hopefully the last scenario for this task :-)

According to the JAX-RPC 1.1 specificiation, the third rule for an operation to be unwrappable: -

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

I have one scenario with the following types defined in the WSDL: -

<element name='lookup'>
 <complexType>
 <sequence>
 </sequence>
 </complexType>
 </element>

 <element name='lookupResponse'>
 <complexType>
 <sequence>
 </sequence>
 </complexType>
 </element>

And on a second scenario I have the following types defined: -

<complexType name='Person'>
 <sequence>
 </sequence>
 </complexType>

 <complexType name='TelephoneNumber'>
 <sequence>
 </sequence>
 </complexType>

wscompile is generating the method in the SEI as: -

public org.jboss.test.ws.jbws1260.LookupResponse lookup() throws
 java.rmi.RemoteException;

and

public org.jboss.test.ws.jbws1260.TelephoneNumber lookup() throws
 java.rmi.RemoteException;

This apears to be handling the unwrapping of the return type differently to the unwrapping of the parameters (as discussed in a previous post).

My question is - If the JAX-RPC specification only mentions complex types that contain a sequence of elements does this mean this scenario does not qualify for unwrapping as there are no elements?

If this type can be unwrapped should the return type of the method be void?