org.apache.juddi.v3.tck
Class UDDISubscriptionListenerImpl
java.lang.Object
java.rmi.server.RemoteObject
java.rmi.server.RemoteServer
java.rmi.server.UnicastRemoteObject
org.apache.juddi.v3.tck.UDDISubscriptionListenerImpl
- All Implemented Interfaces:
- Serializable, Remote, UDDISubscriptionListenerPortType
public class UDDISubscriptionListenerImpl
- extends UnicastRemoteObject
- implements UDDISubscriptionListenerPortType
WebService which implements the UDDI v3 SubscriptionListener API. This service can be
brought during integration testing on the test side. The UDDI server can then
call in to it.
- Author:
- kstam
- See Also:
- Serialized Form
notificationCount
public static Integer notificationCount
notifcationMap
public static Map<Integer,String> notifcationMap
UDDISubscriptionListenerImpl
public UDDISubscriptionListenerImpl()
throws RemoteException
- Throws:
RemoteException
UDDISubscriptionListenerImpl
public UDDISubscriptionListenerImpl(int port)
throws RemoteException
- Throws:
RemoteException
notifySubscriptionListener
public DispositionReport notifySubscriptionListener(NotifySubscriptionListener body)
throws DispositionReportFaultMessage
- Description copied from interface:
UDDISubscriptionListenerPortType
- This API, when implemented by a subscriber and specified in a
subscription, enables the node to deliver notifications to subscription
listeners by invoking a Web service. New, modified, and deleted data that
matches the subscription is passed to notify_subscriptionListener. If the
brief attribute of the subscription is "true", then only the relevant
keys will be sent; full details of the changed data can be accomplished
via the standard get_xx API’s if required. If a particular item that
matches the subscription criteria is deleted during the
notificationInterval, or is changed in such a way that it no longer
matches the criterion defined for the subscription, then these entities
are included in a keyBag containing a deleted element with a value of
"true".
To allow subscribers to determine whether a notification has been lost,
the coverage period of the notification is included. A date/time
indicating the date/time values corresponding to the start and end points
of this is provided. The start date/time used in this call SHOULD align
with the end date/time of the previous call and so fourth. *
If the maxEntities option was specified in the save_subscription call,
the response supplied via this call is limited to that number of
entities. If the node cannot send all of the results in a single
notify_subscriptionListener call, then the node repeatedly invokes the
notify_subscriptionListener service until all information has been
transmitted. In no case will the data sent to notify_subscriptionListener
exceed the maximum message size per the policy of the node.
- Specified by:
notifySubscriptionListener
in interface UDDISubscriptionListenerPortType
- Parameters:
body
- ·
authInfo: This optional argument is an
element that contains an authentication token. Subscription
listener services that wish to restrict who can transmit subscription
data MAY require authInfo for this call, though this is a matter of
client policy.
·
subscriptionResultsList: This list
contains the results for this notification, which consist of the result
structures which are normally returned for standard find_xx or get_xx
APIs, based upon the criteria saved in the subscriptionFilter for the
subscription which is generating this notification. Note that the
chunkToken is not returned with this structure for this API. The
subscriptionResultsList also contains a coveragePeriod structure which
defines the time period over which the node data is compared with the
subscription criterion in order to produce the result set. It provides
the start and end date/time information according to the format described
in Section 5.5.4 Subscription Coverage
Period. The "current" state of registry entries pertaining to
the subscription referenced by the subscriptionKey provided are returned
if they were last changed during the specified time period. See Section
5.5.11.3 Returns for more information
on the subscriptionResultsList’s content.
- Returns:
- returns org.uddi.api_v3.DispositionReport Upon successful
completion, notify_subscriptionListener returns an empty message. Note
that this is being returned by the client supported API.
- Throws:
DispositionReportFaultMessage
- If an error
occurs in processing this API call, a dispositionReport structure is
returned to the caller in a SOAP Fault. In addition to the errors
common to all APIs, the following error information is relevant here:
·
E_fatalError: signifies the client’s failure
to receive notification data. The node is not obligated to
retry.
Copyright © 2004-2013 The Apache Software Foundation. All Rights Reserved.