cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "maomaode (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-919) cxf-codgen-plugin needs to depend on cxf-rt-bindings-soap
Date Mon, 20 Aug 2007 04:37:30 GMT

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

maomaode commented on CXF-919:
------------------------------

Here is the doc http://cwiki.apache.org/confluence/display/CXF20DOC/Maven+Integration+and+Plugin,
It said to include the jaxws frontend, which turns include the soap binding

At moment we just can not put the jaxws/soap dependencies into our code-gen plugin, there's
cyclic dependencies in the testutils module, but hope we can solve it soon.

> 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
>
> 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.


Mime
View raw message