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

This will instruct the http bc that the resolved endpoint should use soap.

On Nov 15, 2007 2:34 PM, Bartosz <[EMAIL PROTECTED]> wrote:

>
> The broker is provided with an address to some external WS and the
> endpoint
> is resolved correctly. JbiSubscription is successful in communicating the
> client. So everything you wrote is true. The problem is that wsn-http
> example uses a SOAP http binding and my external client communicates the
> broker over SOAP. For me the WSN implementation in SM is a blackbox, I'm
> sending SOAP and it is accepted, so I'm expecting to be notified (back)
> using SOAP. JbiSubscription provides my client with a raw XML notification
> (+ the XML declaration (prolog) is added).
>
> --
> View this message in context:
> http://www.nabble.com/WSN2005---SOAP---a-full-featured-external-WSN-client-tf4810818s12049.html#a13767549
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Reply via email to