[
https://issues.apache.org/jira/browse/JUDDI-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925006#action_12925006
]
Kurt T Stam commented on JUDDI-422:
-----------------------------------
Our reasoning is that if you're subscribing to a service you probably want the
base line. So you can add it into your repo. It is new to the client. I think
you can read it both ways, but the point is if your client is going to be able
to receive updates you might as well take this first base line. Seems like it
can't hurt in any case. It enabled us to use this in our federated UDDI setup:
http://juddi.apache.org/docs/3.0/userguide/html/chap-Subscription.html#sect-Two_node_example
Since this is a question I;m going to close this as a jira. Please use our
user-forum for questions. That way more people can chime in and discuss. So
feel free to follow up on the forum. Note that the name just changed, it now
is: [email protected].
Cheers,
--Kurt
> 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.
