[jira] Resolved: (CXF-2005) Missing type in generated WSDL part definition when using int[] arrays with RPC/Literal encoding

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-2005.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.4

> Missing type in generated WSDL part definition when using int[] arrays with RPC/Literal encoding
> ------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2005
>                 URL: https://issues.apache.org/jira/browse/CXF-2005
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.1.3
>         Environment: java version "1.6.0_11", apache-cxf-2.1.3 (with asm-2.2.3)
>            Reporter: Pierre Post
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.1.4
>
>
> CXF seems to generate an incorrect WSDL when using operations with int[] array parameters in web services using the RPC/Literal encoding. The following code
> @WebService(name="MathService", targetNamespace="http://test.backoffice.ciss.lu/service")
> @SOAPBinding(style=SOAPBinding.Style.RPC, use=SOAPBinding.Use.LITERAL)
> public interface MathService {
>     
>     @WebMethod(operationName="ConvertToString")
>     @WebResult(name="stringNumbers")
>     public String[] convertToString(@WebParam(name="intNumbers") int[] numbers);
> }
> generates the WSDL code (extract):
> <wsdl:types>
> 	<xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://jaxb.dev.java.net/array" xmlns="http://jaxb.dev.java.net/array" xmlns:xs="http://www.w3.org/2001/XMLSchema">
>     	<xs:complexType final="#all" name="stringArray">
>         	<xs:sequence>
>             	<xs:element maxOccurs="unbounded" minOccurs="0" name="item" nillable="true" type="xs:string"></xs:element>
>         	</xs:sequence>
>     	</xs:complexType>
> 	</xs:schema>
> </wsdl:types>
> <wsdl:message name="ConvertToString">
> 	<wsdl:part name="intNumbers">
> 	</wsdl:part>
> </wsdl:message>
> <wsdl:message name="ConvertToStringResponse">
> 	<wsdl:part name="stringNumbers" type="ns1:stringArray">
>     </wsdl:part>
> </wsdl:message>
> As you can see, the type information is missing in the first <wsdl:part> tag. The incorrect WSDL obviously produces errors, e.g. when generating the client using the wsdl2java tool:
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -client -verbose http://localhost:8080/CISS_BackOfficeTemplate/services/MathService?wsdl
> wsdl2java - Apache CXF 2.1.3
> WSDLToJava Error:
>  Summary:  Failures: 1, Warnings: 0
>  <<< ERROR!
> The part does not have a type defined. Every part must specify a type from some
> type system. The type can be specified using the built in element or type attrib
> utes or may be specified using an extension attribute.
> org.apache.cxf.tools.common.ToolException:
>  Summary:  Failures: 1, Warnings: 0
>  <<< ERROR!
> The part does not have a type defined. Every part must specify a type from some
> type system. The type can be specified using the built in element or type attrib
> utes or may be specified using an extension attribute.
>         at org.apache.cxf.tools.validator.internal.WSDL11Validator.isValid(WSDL11Validator.java:136)
>         at org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.validate(JAXWSDefinitionBuilder.java:201)
>         at org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.validate(JAXWSDefinitionBuilder.java:61)
>         at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:133)
>         at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:232)
>         at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:83)
>         at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:103)
>         at org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:173)
> The error does not occur when using the (default) Document/Literal encoding or when using Integer[] arrays or List<Integer>. It is possible that the error exists with other primitive types (long, double, etc.) but I haven't tested them.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.