Notification Support

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History
h1. Using notifications

h2. XML clients

In this part, we describe how notifications can be used with SOAP client and services. As an example, just think that all external actors are SOAP ones in the architecture figure above. This really simple sample is composed of several external actors : Some WS notification subscribers which will receive notifications they are interested in; A notification producer which will be in charge of sending notifications to a topic and the DSB which will route notification messages to the right notification subscribers.
{info}It is important to note that in the DSB, the notification engine is a core service a so is automatically exposed as Web service by the SOAP connector. But, even if we only use Web services in this sample, we can also have DSB service clients which directly send subscribe and notify messages to the DSB WSN endpoint itself.{info}
}{code}

There are also some simple Java clients available to ease the developer life:
h2. Simple HTTP Clients

There are also some simple Java clients available which allows the developer to bypass the XML manipulations and directly access to the useful information such as subscription ID, topic, EPR...:
{code:language=java}package org.petalslink.dsb.notification.client.http;

}{code}

The HTTP clients are available in the Maven dependency org.petalslink.dsb:dsb-notification-httpclient.

h1. Configuration