Page History

...

• when not using SOAP /raw HTTP/ the endpoint address has to end with slash, e.g. http://localhost:11111/wsn/NotificationConsumer/^{Image Removed} (http://localhost:11111/wsn/NotificationConsumer^{Image Removed} is wrong - SM will fail to understand this URL) => you have to deploy the WS with a trailing slash in the name (NotificationConsumer/)

• when using properties, you cannot use the trailing slash - http://localhost:11111/wsn/NotificationConsumer/?http.soap=true^{Image Removed} is wrong, http://localhost:11111/wsn/NotificationConsumer?http.soap=true^{Image Removed} is ok (but still it does not make SM use SOAP)

• 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^{Image Removed} . 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^{Image Removed} is the only solution when communication over SOAP is required. 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).

...