cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-3287) cxf-codegen-plugin reports Non-unique body parts! exception
Date Wed, 26 Jan 2011 17:14:44 GMT

    [ https://issues.apache.org/jira/browse/CXF-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987095#action_12987095
] 

Andreas Veithen commented on CXF-3287:
--------------------------------------

Glen,

That is not entirely correct. In WS-I Basic Profile 2.0 the definition of "operation signature"
has changed:

"The Profile defines the "operation signature" to be the fully qualified name of the child
element of SOAP body of the SOAP input message described by an operation in a WSDL binding
and the URI value of the wsa:Action SOAP header block, if present."

The part about the SOAP action was absent in BP 1.1. If cxf-codegen-plugin only checks for
the QName of the child element of the SOAP body without taking into account the SOAP action,
then this is indeed a bug.

> cxf-codegen-plugin reports Non-unique body parts! exception
> -----------------------------------------------------------
>
>                 Key: CXF-3287
>                 URL: https://issues.apache.org/jira/browse/CXF-3287
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.3.2
>         Environment: Windows XP. JSE1.6
>            Reporter: Sean McElroy
>
> When I use the cxf-codegen-plugin maven plugin to generate a client, I get the following
error:
> [ERROR] Failed to execute goal org.apache.cxf:cxf-codegen-plugin:2.3.2:wsdl2java (test-service)
on project verisign-client: Non-unique body parts! In a port, operations must have unique
operation signatures on the wire for successful dispatching. In port {http://schemas.verisign.com/pkiservices/2009/07/enrollment}veriSignCertServiceSOAP,
operations "{http://docs.oasis-open.org/ws-sx/ws-trust/200512/}RequestSecurityToken" and "{http://docs.oasis-open.org/ws-sx/ws-trust/200512/}RequestSecurityToken2"
have the same request body block {http://docs.oasis-open.org/ws-sx/ws-trust/200512/}RequestSecurityToken
-> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the
following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> If I used the axis2-wsdl2code-maven-plugin the client is created as expected.

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