[
https://issues.apache.org/jira/browse/JUDDI-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887213#action_12887213
]
Kurt T Stam commented on JUDDI-402:
-----------------------------------
Hi Jason,
Rereading the spec I think jUDDI is doing the right thing where on an update on
of a (related) business no updates are being sent:
http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908129 (see 5.5.1.1).
They should only be sent if:
1. For related businessEntity:
A related businessEntity (related to the business specified in the businessKey
argument of find_relatedBusinesses API) is considered to be changed if either:
- the related businessEntity is changed, or
- at least one of the two reciprocal publisherAssertions that represents the
relationship is changed.
2. For publisherAssertion:
A publisherAssertion is considered to be changed if the publisher has updated
the publisherAssertion via the set_publisherAssertions, or
add_publisherAssertions APIs.
So if you want to receive updates on an update on a business, you need to
create a subscription on that businessEntity.
Thank you for reporting the issue and please let us know if I misunderstood
your description of the report. It did give me an opportunity to go over the
code and I added some more functionality to the XRegistration (JUDDI-380).
--Kurt
> Two subscription filters not working correctly
> ----------------------------------------------
>
> Key: JUDDI-402
> URL: https://issues.apache.org/jira/browse/JUDDI-402
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.2
> Environment: Tomcat 6.0.10, PostgreSQL 8.4
> Reporter: Jason Brown
> Assignee: Kurt T Stam
> Fix For: 3.0.3
>
>
> When creating a subscription with a filter for find_relatedBusiness a
> subscription is created and a listener shows that notifications are being
> sent, but when changes are made to related businesses no updates are being
> sent. When a subscription is created for a get_assertionStatusReport no
> notifications are sent at all as though no subscription has been created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
