cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-3287) cxf-codegen-plugin reports Non-unique body parts! exception
Date Tue, 05 Apr 2011 21:05:05 GMT

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

Daniel Kulp resolved CXF-3287.
------------------------------

       Resolution: Not A Problem
    Fix Version/s: Invalid
         Assignee: Daniel Kulp


Marking this as not a problem as it's working per spec. 

The trust 1.3 wsdl that you mention is not WS-I BP compliant in that the operation are not
uniquely identifiable as described in the wsdl.   If you try the newer 1.4 wsdl:

http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/cd/ws-trust-1.4.wsdl

then you can see that with the Actions in place, it can generate code.

> 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
>            Assignee: Daniel Kulp
>             Fix For: Invalid
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message