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.
