Package com.silverpeas.notification

Provides an API for pusblishing and for receiving notifications about some topics.

See:
Description

Interface Summary

MessageSubscribingService	Front end of the subscribing service in a specific messaging system.
NotificationPublisher	A publisher of a notification in Silverpeas.
NotificationSubscriber	A subscriber of notifications published on a given topic in Silverpeas.

Class Summary

DefaultNotificationSubscriber	It is the default implementation of the NotificationSubscriber interface.
NotificationPublisherFactory	Factory of notification publishers for beans not managed by an IoC container.
NotificationSource	The source from which a notification was generated.
NotificationTopic	Topic on which notifications are published.
SilverpeasNotification	A notification emitted within the Silverpeas system.

Enum Summary

RegisteredTopics	This enumeration lists all the notification topics that are registered within the Silverpeas Notification System and for which any beans in Silverpeas can subscribe.
SilverpeasNotificationCause	In Silverpeas, the notifications that are sent through the Sivlerpeas Notification System are mainly for business object deletion, creation, ...

Exception Summary

PublishingException	An exception that is thrown when the publication of a notification failed.
SubscriptionException	An exception that is thrown when a subscription failed.

Package com.silverpeas.notification Description

Provides an API for pusblishing and for receiving notifications about some topics. A topic refers the nature of information that will be carried by the notifications; for example, a topic can be related to the actions (add and removal) on the comments over the contents managed in Silverpeas. A notification is a message sent by a publisher over a specific topic. Objects interested by such messages have to subscribe for notifications about this topic; theses are subscribers that will be then informed of the incoming notifications through a callback with the message passed as parameter. The API can also be used for posting messages to several end-points (one to many user communication for example). The API decouples the client from the specific messaging system (JMS, AMQP, ...) used to provide the notification mechanism, so that the underlying MOM system can be changed without any impact. The implementation of this API is a MOM technology-dependent and it is injected through the IoC container within which the Silverpeas components are deployed.