You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Stephen de Vries (JIRA)" <ji...@apache.org> on 2012/05/11 16:36:50 UTC

[jira] [Commented] (CXF-4046) Jaxws client sends bad SOAPAction using client objects from wsimport from a WCF SOAP service.

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

Stephen de Vries commented on CXF-4046:
---------------------------------------

Has there been any update on this issue?  I'm having the exact same problem, also appears only when using a custom header and when performing multiple requests on the same service.

                
> 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, ThisWorksOutInterceptor.java, showbugservice-wcf-vs2008-net35.zip, showbugwsdl.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