Hi all,
I am wondering if there has been any progress on JIRA issue CXF-927?
If not, I'd like to encourage the CXF team to give this issue some
attention. :-)
I guess the provided WSDL file can serve as a test case.
The WSDL at the bottom of this post produces the following interface
public interface ABC {
[...]
public void opA(java.lang.String a);
public void opC(java.lang.String c);
public void opB(java.lang.String b);
}
although, given the <enableWrapperStyle>false</enableWrapperStyle>
declaration in the WSDL file, I would expect it to produce something similar
to:
public interface ABC {
public void opA(java.lang.String a);
public OpCResponse opC(OpC c);
public void opB(java.lang.String b);
}
right?
cheers, Peter
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wsdl:definitions
xmlns:s="http://ws.se/ABC"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
name="ABC"
targetNamespace="http://ws.se/ABC">
<wsdl:types>
<xsd:schema targetNamespace="http://ws.se/ABC"
elementFormDefault="qualified">
<xsd:element name="opA">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="a" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="opAResponse">
<xsd:complexType>
<xsd:sequence/>
</xsd:complexType>
</xsd:element>
<xsd:element name="opB">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="b" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="opBResponse">
<xsd:complexType>
<xsd:sequence/>
</xsd:complexType>
</xsd:element>
<xsd:element name="opC">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="c" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="opCResponse">
<xsd:complexType>
<xsd:sequence/>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name="opA">
<wsdl:part element="s:opA" name="input"/>
</wsdl:message>
<wsdl:message name="opAResponse">
<wsdl:part element="s:opAResponse" name="output"/>
</wsdl:message>
<wsdl:message name="opB">
<wsdl:part element="s:opB" name="input"/>
</wsdl:message>
<wsdl:message name="opBResponse">
<wsdl:part element="s:opBResponse" name="output"/>
</wsdl:message>
<wsdl:message name="opC">
<wsdl:part element="s:opC" name="input"/>
</wsdl:message>
<wsdl:message name="opCResponse">
<wsdl:part element="s:opCResponse" name="output"/>
</wsdl:message>
<wsdl:portType name="ABC">
<wsdl:operation name="opA">
<wsdl:input message="s:opA" name="opA" />
<wsdl:output message="s:opAResponse" name="opAResponse" />
</wsdl:operation>
<wsdl:operation name="opB">
<wsdl:input message="s:opB" name="opB" />
<wsdl:output message="s:opBResponse" name="opBResponse" />
</wsdl:operation>
<wsdl:operation name="opC">
<wsdl:input message="s:opC" name="opC" />
<wsdl:output message="s:opCResponse" name="opCResponse" />
<jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws">
<jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
</jaxws:bindings>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
--
View this message in context:
http://www.nabble.com/WSDL2Java-2.0.3-%28still%29-ignores-enableWrapperStyle----CXF-927-tp14893304p14893304.html
Sent from the cxf-user mailing list archive at Nabble.com.