[
https://issues.apache.org/jira/browse/CXF-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987104#action_12987104
]
Glen Mazza commented on CXF-3287:
---------------------------------
Yes, I believe I stand corrected. I did not know WS-I 2.0[1] was out, it's
actually pretty new (Nov. 2010). Of course, this is not the
cxf-codegen-plugin, but just wsdl2java (the former wraps the latter). 2.0 was
updated to require WS-Addressing
(http://www.ws-i.org/Profiles/BasicProfile-2.0-2010-11-09.html#WSADDR), which
is probably why the definition of operation signature changed.
Only concern I have about this is that we cannot guarantee that a web service
will read the wsa:Action SOAP header (especially from older web services. or if
Addressing is turned off), they would still rely on the input message. But
anyway, yes, it appears that wsdl2java should allow for what you're asking,
providing the wsa:Action SOAP headers values are present and indeed different.
Reopening, thanks.
[1] http://www.ws-i.org/Profiles/BasicProfile-2.0-2010-11-09.html
> 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.
