Apache Muse - WS-BaseNotification - PullPointCreation Capability

Spec name and port type: WS-BaseNotification v1.3, PullPointCreation (WSDL)

Capability URI: http://docs.oasis-open.org/wsn/bw-2/PullPointCreation

Description: This capability implements the WS-N CreatePullPoint operation, which allows a client to create a pullpoint, or a place where the client can go to retrieve notifications produced by the resource on its own time. This is like a semi-broker system, and is not publish-subscribe - the pullpoint that is created by the CreatePullPoint operation will subscribe the resource's notifications and then save them for future retrieval rather than forwarding them.

One cannot add this capability without also deploying the PullPoint resource type. More details are provided in Behavior and Limitations.

Java interface: org.apache.muse.ws.notification.PullPointCreation

JAR file: muse-wsn-api.jar

Default Java implementation: org.apache.muse.ws.notification.impl.SimplePullPointCreation

JAR file: muse-wsn-impl.jar

Action on initialize(): Verifies that the PullPoint resource type has been deployed.

Action on initializeCompleted(): None.

Action on prepareShutdown(): None.

Action on shutdown(): None.

Non-Core Dependencies:

• http://docs.oasis-open.org/wsn/bw-2/PullPoint
  


• http://docs.oasis-open.org/wsn/bw-2/NotificationProducer
  


• http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager
  


• The Abstract WSRF Capability
  

Behavior and Limitations: Calls to createPullPoint() result in the creation of a pullpoint resource; in the default implementation, these pullpoints are persisted as XML files on disk and will be reloaded if the application's container reboots. The type representing pullpoints is any resource type deployed in muse.xml that has the WSN PullPoint capability. If no such resource type is deployed, the capability will fail to initialize, because the type is necessary in order to represent pullpoints in a standards-compliant way.

Initialization parameters: None.