[
https://issues.apache.org/jira/browse/CXF-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189221#comment-13189221
]
Glen Mazza commented on CXF-4046:
---------------------------------
Hi, Mike, this may have zero relation to your problem but the error that is
occurring seems common for it. Note for CXF there are two uniqueness rules
defined in the WS-I basic profile that the WSDL needs to follow -- if that
Microsoft WSDL isn't following these rules, the results may/will be undefined.
Here are the two rules, for this sample WSDL snippet:
<wsdl:portType name="DoubleItPortType">
<wsdl:operation name="DoubleIt">
<wsdl:input message="tns:DoubleItRequest" />
<wsdl:output message="tns:DoubleItResponse" />
</wsdl:operation>
...other operations...
</wsdl:portType>
R2304[1]: The operation "name" attibute must be unique for each operation
within a PortType, i.e., you can't have two operations both having the name
"DoubleIt".
R2710[2]: (effectively) The wsdl:input "message" attribute must be unique for
all operations within the portType, i.e., you can't have two wsdl:inputs using
message "DoubleItRequest".
Question: Is your Microsoft WSDL violating either of the two above rules?
[1] http://www.ws-i.org/profiles/basicprofile-1.1-2004-08-24.html#R2304
[2] http://www.ws-i.org/profiles/basicprofile-1.1-2004-08-24.html#R2710
> Jaxws client sends bad SOAPAction using client objects from wsimport from a
> WCF SOAP service.
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-4046
> URL: https://issues.apache.org/jira/browse/CXF-4046
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.5, 2.5.1
> Reporter: Mike Hurley
> Priority: Minor
> Attachments: CxfJaxwsCustomHttpHeaderBug.zip,
> showbugservice-wcf-vs2008-net35.zip
>
>
> I add a custom HTTP header field to work with our HTTP tunnel server so it
> can route the HTTP request.
> Our SOAP service is exposed from WCF. The attached WCF service is similar to
> what we're using internally. I even made the XML/WSDL namespaces similar.
> Making a call to a second or third (or beyond) method on the same proxy
> object results in the correct SOAP body xml being sent but the SOAPAction
> will always be that of the first method call against the proxy.
> Attached is a Java CXF JAXWS client calling the also attached WCF service.
> The issue seems related to the WSDL exposed. I assume it has something to do
> with WSDL referencing other WSDL.
> The following WSDL didn't have any problem with the way I'm constructing the
> client side (SOAPAction didn't get messed up).
> - The SOAP service exposed at:
> http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL
> - A default Visual Studio 2008 WCF service application (just use the default
> service that gets made)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
