I suppose these things could be fleshed out a bit. Would you mind raising a JIRA about that ? And maybe add some infos on the wiki if you don't mind...
On Nov 15, 2007 4:49 PM, Bartosz <[EMAIL PROTECTED]> wrote: > > > gnodet wrote: > > > > I see now. > > When you subscribe, can you add "?http.soap=true" at the end of the http > > consumer address ? > > Somehting like > > http://myhost/myconsumer?http.soap=true > > > > Ok, it turned out that this is the right direction. Unfortunately it's > only > a part of the answer. With some help of my team I found the right > solution. > You could post it somewhere as guidlines to using WSN. > > The conclusions: > > * when not using SOAP /raw HTTP/ the endpoint address has to end with > slash, e.g. http://localhost:11111/wsn/NotificationConsumer/ > (http://localhost:11111/wsn/NotificationConsumer 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 is wrong, > http://localhost:11111/wsn/NotificationConsumer?http.soap=true 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 > . 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-tf4810818s12049.html#a13773231 > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
