I think the unsubscribe request corresponding to the scenario would be: <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"; xmlns:wsa="http://www.w3.org/2005/08/addressing";> <env:Header> <wsa:To> http://servicemix.org/wsnotification/Subscription/ID-some-host-38972-1188922931357-3-1 </wsa:To> </env:Header> <env:Body> <wsnt:Unsubscribe /> </env:Body> </env:Envelope>
Note that the wsa:To content comes from the SubscribeResponse. On Fri, Sep 12, 2008 at 6:37 PM, kai0411 <[EMAIL PROTECTED]> wrote: > > It was given a message format to 'subscribe' an endpoint for a topic in > http://servicemix.apache.org/example-scenario.html. > What is the format to 'un-subscribe' an endpoint? > I tried tags <Unsubscribe> and <unSubscribe>, but got 'HTTP 500' error. > > > > gnodet wrote: >> >> This is the default behaviour if you don't use a PulPoint. When you >> register a subscription, you give the address of the JBI endpoint in >> the request so that the broker can send you notifications on the >> specified topic. >> >> On Thu, Sep 4, 2008 at 6:36 PM, kai0411 <[EMAIL PROTECTED]> wrote: >>> >>> there is example in http://servicemix.apache.org/example-scenario.html >>> for a >>> 'Pull' notification. Users have to 'pull' their notification from the >>> Broker. >>> How to implement a 'Push' notification, ie. when WSN2005 gets a >>> notification, it would 'push' the notification to a service engine? >>> >>> thanks for help >>> -- >>> View this message in context: >>> http://www.nabble.com/Servicemix-wsn2005-tp19314625p19314625.html >>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com. >>> >>> >> >> >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> >> > > -- > View this message in context: > http://www.nabble.com/Servicemix-wsn2005-tp19314625p19459687.html > Sent from the ServiceMix - Dev mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
