Re: The SOAP action specified on the message, '', does not match the HTTP SOAP Action

[Daniel Kulp]

> On Feb 11, 2016, at 4:22 PM, parthivphoenix  wrote:
> 
> here is wsdl i am using
> 
>  
>  targetNamespace="http://CCO.eClaims.HL7V3.Interface/;
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/;
> xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex;
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
> xmlns:wsa10="http://www.w3.org/2005/08/addressing;
> xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy;
> xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy;
> xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract;
> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/;
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing;
> xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata;
> xmlns:xsd="http://www.w3.org/2001/XMLSchema;
> xmlns:tns="http://CCO.eClaims.HL7V3.Interface/;
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/;
> xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl;
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/;>
> 
>   
>  
> 
> 
> 
>  xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;>
> 
> 
> 
>   
>  
>  
> 
> 
>   
>  
>  
> 
> 
>   
>  
>  
>  
>  
>   
>  
>  
>  
>  
> targetNamespace="http://CCO.eClaims.HL7V3.Interface/Imports;>
>   namespace="http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message"/>
>
>  
> 
>   xmlns:q1="http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message; /> 
>  
> 
>   xmlns:q2="http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message; /> 
>  
> 
>   
> 
>   
>   message="tns:eClaimsHL7v3InterfaceSvc_ProcessMessage_InputMessage" /> 
>   message="tns:eClaimsHL7v3InterfaceSvc_ProcessMessage_OutputMessage" /> 
>  
>  
>  type="tns:eClaimsHL7v3InterfaceSvc">
>   
>  http://schemas.xmlsoap.org/soap/http; /> 
> 
>   
>   
> 
>   encodingStyle="http://www.w3.org/2003/05/soap-encoding; /> 
>  
> 
>   encodingStyle="http://www.w3.org/2003/05/soap-encoding; /> 
>  
>  
>  
> 
>  binding="tns:WSHttpBinding_ITwoWayAsync">
>   location="https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc;
> /> 
> 
> 
> https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc
>  
>  
>  
>  
>  
> 
> 
> 
> and here is the message i am sending 
> 
> 
>  xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope;> soapenv:mustUnderstand="true"
> xmlns="http://www.w3.org/2005/08/addressing;>ProcessMessage
>  xmlns="http://www.w3.org/2005/08/addressing;>https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc xmlns="http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message;>
> 
> 
> but when my application is deployed on  WebSphere i get this message
> 
> 0108 ContainerResp E   The RuntimeException could not be mapped to a
> response, re-throwing to the HTTP container
> javax.xml.ws.soap.SOAPFaultException: The
> SOAP action specified on the message, '', does not match the HTTP SOAP
> Action, 'ProcessMessage'. 
>   at
> org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1363)
>   at
> org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1089)
>   at
> org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.demarshalFaultResponse(DocLitBareMethodMarshaller.java:417)
>   at
> org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:626)
>   at
> org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:566)
>   at
> org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:432)
>   at
> org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:213)
>   at com.sun.proxy.$Proxy65.processMessage(Unknown Source)
>   at
> com.cerner.cco.service.CcoService.processMessageRequest(CcoService.java:131)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>   at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>   at java.lang.reflect.Method.invoke(Method.java:611)
>   at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>   at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
>   at
> 

Re: The SOAP action specified on the message, '', does not match the HTTP SOAP Action

[Daniel Kulp]

The  SOAPAction that it’s talking about may be the HTTP level headers which you 
don’t mention in your message.   Can you capture the HTTP headers and see what 
is there? 

Dan



> On Feb 11, 2016, at 4:22 PM, parthivphoenix  wrote:
> 
> here is wsdl i am using
> 
>  
>  targetNamespace="http://CCO.eClaims.HL7V3.Interface/;
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/;
> xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex;
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
> xmlns:wsa10="http://www.w3.org/2005/08/addressing;
> xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy;
> xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy;
> xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract;
> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/;
> xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing;
> xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata;
> xmlns:xsd="http://www.w3.org/2001/XMLSchema;
> xmlns:tns="http://CCO.eClaims.HL7V3.Interface/;
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/;
> xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl;
> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/;>
> 
>  
> 
> 
> 
> 
>  xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;>
> 
> 
> 
>  
> 
> 
> 
> 
>  
> 
> 
> 
> 
>  
> 
> 
> 
> 
>  
> 
> 
> 
> 
>targetNamespace="http://CCO.eClaims.HL7V3.Interface/Imports;>
>  namespace="http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message"/>
>   
> 
> 
>  xmlns:q1="http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message; /> 
> 
> 
>  xmlns:q2="http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message; /> 
> 
> 
>  
> 
>  
>  message="tns:eClaimsHL7v3InterfaceSvc_ProcessMessage_InputMessage" /> 
>  message="tns:eClaimsHL7v3InterfaceSvc_ProcessMessage_OutputMessage" /> 
> 
> 
>  type="tns:eClaimsHL7v3InterfaceSvc">
>  
> http://schemas.xmlsoap.org/soap/http; /> 
> 
>  
>  
> 
>  encodingStyle="http://www.w3.org/2003/05/soap-encoding; /> 
> 
> 
>  encodingStyle="http://www.w3.org/2003/05/soap-encoding; /> 
> 
> 
> 
> 
>  binding="tns:WSHttpBinding_ITwoWayAsync">
>  location="https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc;
> /> 
> 
> 
> https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc
>  
> 
> 
> 
> 
> 
> 
> 
> and here is the message i am sending 
> 
> 
>  xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope;> soapenv:mustUnderstand="true"
> xmlns="http://www.w3.org/2005/08/addressing;>ProcessMessage
>  xmlns="http://www.w3.org/2005/08/addressing;>https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc xmlns="http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message;>
> 
> 
> but when my application is deployed on  WebSphere i get this message
> 
> 0108 ContainerResp E   The RuntimeException could not be mapped to a
> response, re-throwing to the HTTP container
>javax.xml.ws.soap.SOAPFaultException: The
> SOAP action specified on the message, '', does not match the HTTP SOAP
> Action, 'ProcessMessage'. 
>   at
> org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1363)
>   at
> org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1089)
>   at
> org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.demarshalFaultResponse(DocLitBareMethodMarshaller.java:417)
>   at
> org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:626)
>   at
> org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:566)
>   at
> org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:432)
>   at
> org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:213)
>   at com.sun.proxy.$Proxy65.processMessage(Unknown Source)
>   at
> com.cerner.cco.service.CcoService.processMessageRequest(CcoService.java:131)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>   at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>   at java.lang.reflect.Method.invoke(Method.java:611)
>   at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
>   at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at
> 

Re: The SOAP action specified on the message, '', does not match the HTTP SOAP Action

[parthivphoenix]

The message had header right?


http://www.w3.org/2005/08/addressing;>ProcessMessage 
 
xmlns="http://www.w3.org/2005/08/addressing;>https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc



--
View this message in context: 
http://cxf.547215.n5.nabble.com/The-SOAP-action-specified-on-the-message-does-not-match-the-HTTP-SOAP-Action-tp562966p5765855.html
Sent from the cxf-user mailing list archive at Nabble.com.

Re: The SOAP action specified on the message, '', does not match the HTTP SOAP Action

[Daniel Kulp]

> On Feb 12, 2016, at 2:47 PM, parthivphoenix  wrote:
> 
> The message had header right?

No.  The HTTP headers.The SOAPAction is something that is sent in the HTTP 
headers.   For soap 1.2, that would be an “action" param on the Content-Type.   
 When using ws-addressing, it has to match the Action soap header as well.   

Dan


> 
> 
>  xmlns="http://www.w3.org/2005/08/addressing;>ProcessMessage 
> 
> xmlns="http://www.w3.org/2005/08/addressing;>https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc
> 
> 
> 
> --
> View this message in context: 
> http://cxf.547215.n5.nabble.com/The-SOAP-action-specified-on-the-message-does-not-match-the-HTTP-SOAP-Action-tp562966p5765855.html
> Sent from the cxf-user mailing list archive at Nabble.com.

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Re: The SOAP action specified on the message, '', does not match the HTTP SOAP Action

[parthivphoenix]

here is wsdl i am using

 
http://CCO.eClaims.HL7V3.Interface/;
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/;
xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex;
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
xmlns:wsa10="http://www.w3.org/2005/08/addressing;
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy;
xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy;
xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract;
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/;
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing;
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata;
xmlns:xsd="http://www.w3.org/2001/XMLSchema;
xmlns:tns="http://CCO.eClaims.HL7V3.Interface/;
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl;
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/;>

   
  



http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;>



   
  
  


   
  
  


   
  
  
  
  
   
  
  
  
  
http://CCO.eClaims.HL7V3.Interface/Imports;>
  http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message"/>

  

  http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message; /> 
  

  http://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message; /> 
  

   

   
   
   
  
  

   
  http://schemas.xmlsoap.org/soap/http; /> 

   
   

  http://www.w3.org/2003/05/soap-encoding; /> 
  

  http://www.w3.org/2003/05/soap-encoding; /> 
  
  
  


  https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc;
/> 

 
https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svc
 
  
  
  
  



and here is the message i am sending 


http://www.w3.org/2003/05/soap-envelope;>http://www.w3.org/2005/08/addressing;>ProcessMessage
http://www.w3.org/2005/08/addressing;>https://hl7.ws.cancercare.on.ca/InboundHL7InterfaceSvc/eClaimsHL7v3InterfaceSvc.svchttp://CCO.eClaims.HL7V3.Interface.InterfaceSchemas.HL7Message;>


but when my application is deployed on  WebSphere i get this message

 0108 ContainerResp E   The RuntimeException could not be mapped to a
response, re-throwing to the HTTP container
 javax.xml.ws.soap.SOAPFaultException: The
SOAP action specified on the message, '', does not match the HTTP SOAP
Action, 'ProcessMessage'. 
at
org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1363)
at
org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1089)
at
org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarshaller.demarshalFaultResponse(DocLitBareMethodMarshaller.java:417)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:626)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:566)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:432)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:213)
at com.sun.proxy.$Proxy65.processMessage(Unknown Source)
at
com.cerner.cco.service.CcoService.processMessageRequest(CcoService.java:131)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
at

Re: The SOAP action specified on the message, '', does not match the HTTP SOAP Action

[Daniel Kulp]

It looks like you don't have ws-addressing turned on.   If you turn on ws-
addressing, then the header should have the action and other addressing 
headers added to it.

The WSDL you pointed to actually has a WS-SecurityPolicy policy fragment in 
it.   Thus, if you use CXF 2.2.x and add the security/policy/addressing 
modules (or use the big bundle), it should be automatic. The policy engine 
would see the wsaw:UsingAddressing/ element in the policy and automatically 
turn on the addressing.

Dan


On Sun May 10 2009 8:04:54 am Niels Bo wrote:
 Hi

 I have generated a client (wsdl2jave) from this wsdl:
 http://api.rkd.reuters.com/schemas/wsdl/TokenManagement_1_HttpsAndAnonymous
.wsdl

 But I receive this error back: The SOAP action specified on the message,
 '', does not match the HTTP SOAP Action
 The in and out messages are below.

 I can see that CXF does not put any SoapAction in the soap:header as
 expected by the reciving service. And as far as I have debugged this is the
 behviour in SoapPreProtocolOutInterceptor when version is Soap12.

 Is there an error in the service or CXF, that I should report?
 But how can I fix this now? Make my own version of
 SoapPreProtocolOutInterceptor??


 Best regards
 Niels Bo

 INFO: Outbound Message
 ---
 ID: 1
 Address:
 https://api.rkd.reuters.com/api/2006/05/01/TokenManagement_1.svc/Anonymous
 Encoding: UTF-8
 Content-Type: application/soap+xml;
 action=http://www.reuters.com/ns/2006/05/01/webservices/rkd/TokenManagemen
t_1/CreateServiceToken_1 Headers: {Accept=[*/*]}
 Payload: soap:Envelope
 xmlns:soap=http://www.w3.org/2003/05/soap-envelope;soap:Header
 /soap:Bodyns2:CreateServiceToken_Request_1 

 INFO: Inbound Message
 
 ID: 1
 Encoding: UTF-8
 Content-Type: application/soap+xml
 Headers: {X-Powered-By=[ASP.NET], X-AspNet-Version=[2.0.50727],
 connection=[Keep-Alive], Date=[Sun, 10 May 2009 11:19:54 GMT],
 transfer-encoding=[chunked], Server=[Microsoft-IIS/6.0],
 content-type=[application/soap+xml], Via=[1.1 RKDAPI],
 Cache-Control=[private]}
 Payload: ?xml version=1.0 encoding=UTF-8?
 s:Envelope xmlns:a=http://www.w3.org/2005/08/addressing;
 xmlns:s=http://www.w3.org/2003/05/soap-envelope;s:Headera:Action
 s:mustUnderstand=1http://www.reuters.com/ns/2006/05/01/webservices/rkd/F
aults_1/Fault_1_Reply/a:Action/s:Headers:Bodys:Faults:Codes:Value
s:Receiver/s:Values:Subcodes:Value
 xmlns:a=http://www.reuters.com/ns/2006/05/01/webservices/rkd/Faults_1;a:G
eneral_UnhandledException/s:Value/s:Subcode/s:Codes:Reasons:Text
 xml:lang=en-GBThe SOAP action specified on the message, '', does not
 match the HTTP SOAP Action, ...

-- 
Daniel Kulp
dk...@apache.org
http://www.dankulp.com/blog

Re: The SOAP action specified on the message, '', does not match the HTTP SOAP Action

[Niels Bo]

Thanks!
That solved the problem.

Niels


dkulp wrote:
 
 
 It looks like you don't have ws-addressing turned on.   If you turn on ws-
 addressing, then the header should have the action and other addressing 
 headers added to it.
 
 The WSDL you pointed to actually has a WS-SecurityPolicy policy fragment
 in 
 it.   Thus, if you use CXF 2.2.x and add the security/policy/addressing 
 modules (or use the big bundle), it should be automatic. The policy
 engine 
 would see the wsaw:UsingAddressing/ element in the policy and
 automatically 
 turn on the addressing.
 
 Dan
 
 
 On Sun May 10 2009 8:04:54 am Niels Bo wrote:
 Hi

 I have generated a client (wsdl2jave) from this wsdl:
 http://api.rkd.reuters.com/schemas/wsdl/TokenManagement_1_HttpsAndAnonymous
.wsdl

 But I receive this error back: The SOAP action specified on the message,
 '', does not match the HTTP SOAP Action
 The in and out messages are below.

 I can see that CXF does not put any SoapAction in the soap:header as
 expected by the reciving service. And as far as I have debugged this is
 the
 behviour in SoapPreProtocolOutInterceptor when version is Soap12.

 Is there an error in the service or CXF, that I should report?
 But how can I fix this now? Make my own version of
 SoapPreProtocolOutInterceptor??


 Best regards
 Niels Bo

 INFO: Outbound Message
 ---
 ID: 1
 Address:
 https://api.rkd.reuters.com/api/2006/05/01/TokenManagement_1.svc/Anonymous
 Encoding: UTF-8
 Content-Type: application/soap+xml;
 action=http://www.reuters.com/ns/2006/05/01/webservices/rkd/TokenManagemen
t_1/CreateServiceToken_1 Headers: {Accept=[*/*]}
 Payload: soap:Envelope
 xmlns:soap=http://www.w3.org/2003/05/soap-envelope;soap:Header
 /soap:Bodyns2:CreateServiceToken_Request_1 

 INFO: Inbound Message
 
 ID: 1
 Encoding: UTF-8
 Content-Type: application/soap+xml
 Headers: {X-Powered-By=[ASP.NET], X-AspNet-Version=[2.0.50727],
 connection=[Keep-Alive], Date=[Sun, 10 May 2009 11:19:54 GMT],
 transfer-encoding=[chunked], Server=[Microsoft-IIS/6.0],
 content-type=[application/soap+xml], Via=[1.1 RKDAPI],
 Cache-Control=[private]}
 Payload: ?xml version=1.0 encoding=UTF-8?
 s:Envelope xmlns:a=http://www.w3.org/2005/08/addressing;
 xmlns:s=http://www.w3.org/2003/05/soap-envelope;s:Headera:Action
 s:mustUnderstand=1http://www.reuters.com/ns/2006/05/01/webservices/rkd/F
aults_1/Fault_1_Reply/a:Action/s:Headers:Bodys:Faults:Codes:Value
s:Receiver/s:Values:Subcodes:Value
 xmlns:a=http://www.reuters.com/ns/2006/05/01/webservices/rkd/Faults_1;a:G
eneral_UnhandledException/s:Value/s:Subcode/s:Codes:Reasons:Text
 xml:lang=en-GBThe SOAP action specified on the message, '', does not
 match the HTTP SOAP Action, ...
 
 -- 
 Daniel Kulp
 dk...@apache.org
 http://www.dankulp.com/blog
 
 

-- 
View this message in context: 
http://www.nabble.com/The-SOAP-action-specified-on-the-message%2C-%27%27%2C-does-not-match-the-HTTP-SOAP-Action-tp23469494p23528975.html
Sent from the cxf-user mailing list archive at Nabble.com.