You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2011/01/25 22:43:46 UTC

[jira] Commented: (CXF-3287) cxf-codegen-plugin reports Non-unique body parts! exception

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

Glen Mazza commented on CXF-3287:
---------------------------------

The Axis2 method is not WS-I Basic Profile compliant, GlassFish Metro would also complain[1] if you attempted to do that.

See: http://www.ws-i.org/profiles/basicprofile-1.1.html#R2710

It's too dangerous, because if you had web service GiveEmployeeVacationInHawaii(EmployeeID) and FireEmployee(EmployeeID) those employees in one category could end up having the other method called for them when you just send the EmployeeID.

Glen

[1] http://www.jroller.com/gmazza/date/20090101

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