[
https://issues.apache.org/jira/browse/CXF-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189243#comment-13189243
]
Glen Mazza commented on CXF-4046:
---------------------------------
I would say relying on the JAX-WS generated objects (using wsdl2java) to make
your SOAP calls is the best way. (See links #43 and #44 for
handler/interceptor usage if needed/desired:
http://www.jroller.com/gmazza/entry/blog_article_index). If that works, good,
but if there is really an underlying CXF bug in the your original method, I can
try to replicate it on my side.
It's more difficult for me to test a Windows WSP (my laptop will dual-boot to
Windows, but I normally use Java & Linux for everything). Question: You
linked above to a WSDL that apparently does *not* cause the problem, but what
is the WSDL that does create it? If you can't send it to me for security
reasons (that's fine), if you want to send me a minimal anonymous WSDL that
would reproduce the error, I can try to duplicate it on my own side with a Java
WSP.
> 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
>
>
> 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
