[jira] Resolved: (CXF-919) cxf-codgen-plugin needs to depend on cxf-rt-bindings-soap

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

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

Daniel Kulp resolved CXF-919.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3


The wsdl2java mojo now uses the project dependencies as well.   If the project depends on soap, it will be available.

> cxf-codgen-plugin needs to depend on cxf-rt-bindings-soap
> ---------------------------------------------------------
>
>                 Key: CXF-919
>                 URL: https://issues.apache.org/jira/browse/CXF-919
>             Project: CXF
>          Issue Type: Bug
>          Components: Build system
>    Affects Versions: 2.0.1, 2.1
>         Environment: Maven version: 2.0.7
> Java version: 1.5.0_12
> OS name: "linux" version: "2.6.11-1.1369_fc4smp" arch: "i386"
>            Reporter: John Williams
>             Fix For: 2.0.3
>
>
> The wsdl2java goal of the cxf-codegen-plugin silently generates incorrect code because it is not declared to depend on cxf-rt-bindings-soap.  The problem seems to occur when using a SOAP binding with RPC-style encoding for a message part associated with a schema element (i.e. <wsdl:part name="..." element="...").  The symptom is that an incorrect @WebParam annotation is generated, ultimately causing a CXF-based client to marshall its arguments incorrectly.
> I considered the possibility that the behavior *without* the dependency on cxf-rt-bindings-soap is more correct, but my reading of section 3.5 of the WSDL 1.1 spec suggests that this is not the case.
> Needless to say, adding the missing dependency fixed the problem, but it took me many hours to discover this solution.

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