Re: http:soap-consumer - SOAP Header lost

[gmotts]

Many thanks! - I did find a work around, if I use the http-endpoint instead
of the http-soap-consumer endpoint I can disable parsing the SOAP header by
setting the soap property to "false"

Here's the one that worked:

<http:endpoint service="b:AbwsHttpConsumerSvc"
               endpoint="AbwsHttpConsumerSvcPort"
               interfaceName="b:AsyncBridgeInterface"
               targetService="b:asyncBridge"      
               locationURI="http://localhost:8192/bridge/";                      
  
               role="consumer" 
               targetEndpoint="asyncBridgeEndpoint"
               defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; 
               soap="no"
               wsdlResource="classpath:EagleSchedulingService.wsdl"/>

Here's the http-soap-consumer endpoint, there is no way to disable parsing
the soap header which may be considered a bug:

<http:endpoint service="b:AbwsHttpConsumerSvc"
               endpoint="AbwsHttpConsumerSvcPort"
               interfaceName="b:AsyncBridgeInterface"
               targetService="b:asyncBridge"      
               locationURI="http://localhost:8192/bridge/";                      
  
               role="consumer" 
               targetEndpoint="asyncBridgeEndpoint"
               defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; 
               soap="no"
               wsdlResource="classpath:EagleSchedulingService.wsdl"/>

-Gary

"Hi,

You can  get org.apache.servicemix.soap.headers property(as a Map)  
from NormalizedMessage.

Freeman"
-- 
View this message in context: 
http://www.nabble.com/http%3Asoap-consumer---SOAP-Header-lost-tp25441155p25452517.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.