Asynchronous subscription notification intervals
------------------------------------------------
Key: JUDDI-423
URL: https://issues.apache.org/jira/browse/JUDDI-423
Project: jUDDI
Issue Type: Bug
Components: core
Affects Versions: 3.0.3
Environment: Apache Tomcat 6.0.29, PostgreSQL 8.4
Reporter: Jason Brown
Assignee: Kurt T Stam
Priority: Minor
When using any asynchronous subscription using a filter other than find_service
notifications are sent regularly at the specified notifcationInterval
regardless of whether or not there is actually a change to the applicable
entities. This is not the case when using a find_service subscriptionFilter,
notifications are only sent when changes are made to the applicable entities.
Which of these is the intended behavior? The specification is vague on this
issue, stating in one place that "When asynchronous notifications are
requested, subscriptions provide information on new, changed or deleted
entities within a registry that occur after the point in time that the
subscription is registered" (Section 5.5.1) but states that
notificationIntervals "specifies how often change notifications are to be
provided to a subscriber." (Section 5.5.8.2). Other products tend to follow the
model jUDDI follows when using a non find_service filter (i.e. sending a
notification at every notificationInterval).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
