Example code for common tasks that your WS-Notification applications can perform.
For an overview of how applications can use the notification broker, see WS-Notification - how client applications interact at runtime.
The code examples listed in this topic use the following WebSphere Application Server APIs and SPIs:
com.ibm.websphere.sib.wsn.AbsoluteOrRelativeTime; com.ibm.websphere.sib.wsn.CreatePullPoint; com.ibm.websphere.sib.wsn.CreatePullPointResponse; com.ibm.websphere.sib.wsn.Filter; com.ibm.websphere.sib.wsn.GetMessages; com.ibm.websphere.sib.wsn.GetMessagesResponse; com.ibm.websphere.sib.wsn.NotificationMessage; com.ibm.websphere.sib.wsn.TopicExpression; com.ibm.websphere.webservices.soap.IBMSOAPFactory; com.ibm.websphere.wsaddressing.EndpointReference; com.ibm.websphere.wsaddressing.WSAConstants; com.ibm.wsspi.wsaddressing.EndpointReferenceManager;
A single application can be coded to perform several WS-Notification tasks. Use the following examples to help you code these tasks into your WS-Notification applications:
Your applications can also use WS-Notification to receive event notifications generated by other clients of the service integration bus such as JMS clients. This is described in Use pattern for WS-Notification as an entry or exit point to the service integration bus and Providing access for WS-Notification applications to an existing bus topic space. For information about developing applications for a mixed clients solution, including cross-streaming from a JMS client, see Sharing event notification messages with other bus client applications.