This exchange is sent to the endpoint identified by the "endpoint"
variable. If this one points to an http endpoint it will work without any
problems. As this endpoint is created by resolving an EPR, if the address
begins with http://, it will be resolved to a dynamic http endpoint and
should be sent to the http bc.
On Nov 15, 2007 1:51 PM, Bartosz <[EMAIL PROTECTED]> wrote:
>
> For those who are not familiar with WS-Notification implementation used in
> SM
> I did a fragment of org.apache.servicemix.wsn.jbi.JbiSubscription source
> code:
>
> @Override
> protected void doNotify(final Element content) {
> try {
> DeliveryChannel channel = getContext().getDeliveryChannel();
> MessageExchangeFactory factory =
> channel.createExchangeFactory(endpoint);
> InOnly inonly = factory.createInOnlyExchange();
> NormalizedMessage msg = inonly.createMessage();
> inonly.setInMessage(msg);
> msg.setContent(new DOMSource(content));
> getLifeCycle().sendConsumerExchange(inonly, processor);
> } catch (JBIException e) {
> log.warn("Could not deliver notification", e);
> }
> }
>
>
> This part is used to sent notification to a consumer (variable 'endpoint'
> -
> the resolved consumer). Is it possible to use HTTP binding in the middle
> of
> such a communication ? ...
> --
> View this message in context:
> http://www.nabble.com/WSN2005---SOAP---a-full-featured-external-WSN-client-tf4810818s12049.html#a13766938
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
