juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Closed: (JUDDI-422) Question about initial subscription notification
Date Tue, 26 Oct 2010 15:54:24 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kurt T Stam closed JUDDI-422.

    Resolution: Not A Problem

We can reopen if our discussion on the user forum results in a different conclusion on how
this is supposed to work.

> Question about initial subscription notification
> ------------------------------------------------
>                 Key: JUDDI-422
>                 URL: https://issues.apache.org/jira/browse/JUDDI-422
>             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
> After saving an asynchronous subscription the initial notification to the listener lists
all of the applicable items in the subscription, although the specification is not entirely
clear on this issue, the beginning of Section 5.5.1 states "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," which
would seem to indicate that the initial message should only contain information about these
entities if they had been created, changed or deleted after the subscription was registered,
otherwise the inital notification from the subscription would contain no entities provided
there had been no changes to the registry. Is there somewhere else in the specification that
makes this behavior expected? We have seen the intial message done both ways from different
products and are attempting to find the reasoning behind why jUDDI performs this way, so clients
can be expecting correct behavior. Any information would be greatly appreciated. Thanks. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message