Follow up question. I found this in the UDDI spec under the subscription API, save subscription
bindingKey: This optional argument of type anyURI specifies the bindingTemplate which the node is to use to deliver notifications to subscription listeners. It is only required when asynchronous notifications are used. This bindingTemplate MUST define either a Web service that implements notify_subscriptionListener (see below), or an email address to receive the notifications. If a notify_subscriptionListener Web service is identified, the node invokes it to deliver notifications. If an email address is identified, the node delivers notifications via email to the address supplied. When notifications are delivered via email, the body of the email contains the body of the SOAP message, which would have been sent to the notify_subscriptionListener service if that option had been chosen. The publisher making the subscription request MUST own the bindingTemplate. If this argument is not supplied, no notifications are sent, although subscribers may still use the get_subscriptionResults API to obtain subscription results. See Section 5.5.11get_subscriptionResults for details. If email delivery to the specified address fails, nodes MAY attempt re-delivery, but are not obligated to do so. Depending upon node policy, excessive delivery failures MAY result in cancellation of the corresponding subscription. The question is, is this how jUDDI is implemented? Are callbacks supported using this mechanism or is it only via the jUDDI API? If so, then it looks like there are two ways to setup a callback subscription. Use the jUDDI API method, or using the UDDI saveSubscription and define the binding template key representing the call back endpoint. (which would mean that the jUDDI api is a bit redundant) On Wed, Apr 3, 2013 at 12:29 PM, Kurt T Stam <[email protected]> wrote: > On 3/30/13 8:49 AM, Alex O'Ree wrote: >> >> With the client side subscript api from the jUDDI service, there's a >> mechanism to add a callback subscription, delete a callback >> subscription, but I don't see anything for getting a list of current >> client subscriptions, or "my" subscriptions. >> >> Are these subscriptions listed via the UDDI Subscription API? the unit >> test doesn't appear to cover this use case. > > Yeah you use: > > http://svn.apache.org/repos/asf/juddi/tags/juddi-3.1.3/juddi-core/src/main/java/org/apache/juddi/api/impl/UDDISubscriptionImpl.java > > List<Subscription> getSubscriptions( > @WebParam(name = "authInfo", targetNamespace = > "urn:uddi-org:api_v3") > String authInfo) > > which should find all subscriptions for the publisher.
