The classes the wsimport generated create an extra wrapper element in the response

[Mika Tapanainen]

Hello,

I'm using the wsimport.bat in the Websphere 7 and when the generated java classes create the response there is an extra element I don't want.

In the response is the element XXXResponse

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <dlwmin:XXXResponse xmlns:dlwmin="XXX" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <ns7:YYY xmlns:ns7="xyz" xmlns="xyzz">
                  ...
         </ns7:YYY>
      </dlwmin:XXXResponse>
   </soapenv:Body>
</soapenv:Envelope>

and I think it is from the wsdl operation element of the portType element:

<portType name="ABC">
	<operation name="XXX">
		<input message="tns:AAA"/>
		<output message="tns:YYY"/>
	</operation>
</portType>

I would like the response to be:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
         <ns7:YYY xmlns:ns7="xyz" xmlns="xyzz">
                  ...
         </ns7:YYY>
   </soapenv:Body>
</soapenv:Envelope>

This is because our customers currently receive this kind of messages from the old webservice implementation.

Is it possible to get rid of the XXXResponse element?

BR,

Mika

[Mika Tapanainen]

I tried this:

http://stackoverflow.com/questions/7032381/java-soap-wsimport-force-wrapped-binding-from-document-literal-wrapped-wsdl

and the binding.xml contained the following value:

<enableWrapperStyle>false</enableWrapperStyle>

but this didn't work for me. Actually the generated source classes are identical without binding, with the value false and with the value true (except the wsimport generates the methods everytime different order).

If someone has experience in this field it would be nice to hear.

[Mika Tapanainen]

It is maybe so that wsimport doesn't read the

<enableWrapperStyle>false</enableWrapperStyle>

element. If I change the element:

<enableWrapperStyles>false</enableWrapperStyles>

there is no error message. Only if the file is not correct XML there comes an error message.

[Mika Tapanainen]

The binding.xml is not needed in this case.

The resolution was the add the annotation

...
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
public class ServiceXXXImpl implements ServiceXXX

in the class level of the service implementation class. There is same annotation in the interface, but it seems that the service implementation class doesn't inherit the annotations. Maybe it is said also in the JAX-WS specification:

3.4.1 Inheritance
WSDL 1.1 does not define a standard representation for the inheritance of wsdl:portType elements.

see more for example: http://download.oracle.com/otndocs/jcp/jaxws-2_2a-mrel4-eval-spec/