Re: WSN2005 & SOAP - a full-featured external WSN client

[RonnieSpike <ro...@nerdshack.com>]

&http.soapVersion=1.1 is no longer necessary (ServiceMix 3.2.3). In fact,
SOAP UI highlights &http.soapVersion=1.1 as incorrect syntax and ServiceMix
does, indeed, throw an exception when &http.soapVersion=1.1 is included in
the consumer endpoint. When not included, the subscribe, notify, consumer
receives notification scenario worked for me.


Bartosz wrote:
> 
> 
>    * when using http.soap=true, you have to use http.soapVersion=1.x, e.g.
> http://localhost:11111/wsn/NotificationConsumer?http.soap=true&http.soapVersion=1.1
> . It does not work without the http.soapVersion=1.x property. 
> 
> 
> To sum up:
> http://localhost:11111/wsn/NotificationConsumer?http.soap=true&http.soapVersion=1.1 
> is the solution. Other options cause SM to throw an exception while
> parsing the address or while trying to access address that does not exist
> (404), or make the XFire generate a fault (no SOAP envelope present).
> 
> Thanks a lot for help.
> 
> 

-- 
View this message in context: http://www.nabble.com/WSN2005---SOAP---a-full-featured-external-WSN-client-tp13764611p20510558.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.