[
https://issues.apache.org/jira/browse/JUDDI-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883015#action_12883015
]
ShengTao Dong commented on JUDDI-403:
-------------------------------------
//The summary of step is below, they are all in one method.
//First subscript a subscription with categories those are category bags, and a
notifyServiceBindingKey that point a web service that has been registered.
//And will return a subscriptionKey that is generated by juddi.
String subscriptionKey = sub.subscribe(categories, notifyServiceBindingKey);
//This is a wrap method, in this method, it call the saveSubscription() .
//Then get subscription result list with the key, and it would succeed, that
means I've got all result those I wanted in this subscription.
SubscriptionResultsList srList = sub.subscribe(subscriptionKey, chunkToken);
//This is a wrap method, it call getSubscriptionResults()
//But after a while, that depend on the time that is set in the remote server,
in my environment, it's 5 second, the remote server will call my notify web
//service and distribute the result list again, after this, it would do it
again.
> After using getSubscriptionResults operation getting the services from
> master-registry, the registry shouldn't call notify interface again for the
> same services
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JUDDI-403
> URL: https://issues.apache.org/jira/browse/JUDDI-403
> Project: jUDDI
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.0.1
> Reporter: ShengTao Dong
> Assignee: Kurt T Stam
>
> After using getSubscriptionResults operation getting the services from
> master-registry with a subscription key, the services had been gotten from
> the master-registry, so It's reasonable that the master registry should not
> call the notify interface to distribute these services because the subscript
> operation used same subscription key, but it did, It made the distributed
> action was done twice, and also made some confusion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
