|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (5)
View Page History
...
h1. Abstract h2. Documentation
As a result of both [SYNERGY project|synergy:SYNERGY Overview] and [Genesis project|genesis:Genesis Overview] we have
implemented a PEtALS Service Engine - a JBI component - that act as a "NotificationBroker", as described in
implemented a PEtALS Service Engine - a JBI component - that act as a "NotificationBroker", as described in
the [OASIS WS-BrokeredNotification specification | http://docs.oasis-open.org/wsn/wsn-ws_brokered_notification-1.3-spec-os.pdf].
For a full description of this component, please refer to the following documentation ([wsnotification:*tip*|#tips]) :
{center}
{viewpdf:petals-se-WsNotificationBroker.pdf|height=850}
{viewpdf:petals-se-WsNotificationBroker.pdf|height=850}
...h3. Source code links
Main component source code can be found on Synergy forge : [Synergy SVN repository | https://forge.ebmwebsourcing.com/plugins/scmsvn/viewcvs.php/?root=synergy] (component source code in "trunk/EBM" folder.
Main component source code can be found on Synergy forge : [Browse Synergy SVN repository; EBM folder |https://forge.ebmwebsourcing.com/plugins/scmsvn/viewcvs.php/trunk/EBM/?root=synergy].
{note}
As some part of source code use "svn:externals" links, please check out using using following links :
svn checkout svn://forge.ebmwebsourcing.com/svnroot/synergy
{note}
{note}
As some part of source code use "svn:externals" links, please check out using using following links :
svn checkout svn://forge.ebmwebsourcing.com/svnroot/synergy
{note}