[
https://issues.apache.org/jira/browse/JUDDI-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647450#comment-13647450
]
Alex O'Ree commented on JUDDI-606:
----------------------------------
I just reviewed the code for the subscription api tests. It's really a minimal
testing scenario and needs to be augmented. To give you an idea, I just setup a
subscription for find_business changes, then added a new business ( as a
different user) and then called getSubscriptionResults. No results were
returned.
I did try a getBusinessDetails subscription and that appears to work correctly.
I also ran into a strange problem. I have four subscriptions defined where are
listed below. When fetching the getSubscriptionResults for each subscription, 3
of 4 give me an empty publisher assertion report (none were expected but only 1
of 4 was). The 4th was a business change which was expected (get business
details). So something isn't quite right and its obvious that it needs more
testing (and cases)
===============================
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<subscription xmlns:ns2="urn:uddi-org:api_v3" xmlns:ns3="urn:uddi-org:sub_v3"
brief="false">
<ns3:subscriptionKey>uddi:juddi.apache.org:f969c725-5826-41e9-8da3-3f74a3926256</ns3:subscriptionKey>
<ns3:subscriptionFilter>
<ns2:get_assertionStatusReport>
<ns2:completionStatus>status:both_incomplete</ns2:completionStatus>
</ns2:get_assertionStatusReport>
</ns3:subscriptionFilter>
<ns3:expiresAfter>2014-05-01T16:50:05.999-04:00</ns3:expiresAfter>
</subscription>
===============================
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<subscription xmlns:ns2="urn:uddi-org:api_v3" xmlns:ns3="urn:uddi-org:sub_v3"
brief="false">
<ns3:subscriptionKey>click to edit</ns3:subscriptionKey>
<ns3:subscriptionFilter>
<ns2:find_business>
<ns2:name xml:lang="">%</ns2:name>
</ns2:find_business>
</ns3:subscriptionFilter>
<ns3:expiresAfter>2014-05-01T21:06:59.119-04:00</ns3:expiresAfter>
</subscription>
===============================
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<subscription xmlns:ns2="urn:uddi-org:api_v3" xmlns:ns3="urn:uddi-org:sub_v3"
brief="false">
<ns3:subscriptionKey>uddi:juddi.apache.org:ded29277-08c9-4b76-bd15-ea3ec82270b4</ns3:subscriptionKey>
<ns3:subscriptionFilter>
<ns2:get_businessDetail>
<ns2:businessKey>uddi:juddi.apache.org:224166ab-a017-4b25-b85f-c1e3996da253</ns2:businessKey>
</ns2:get_businessDetail>
</ns3:subscriptionFilter>
<ns3:expiresAfter>2014-05-02T07:20:20.051-04:00</ns3:expiresAfter>
</subscription>
===============================
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<subscription xmlns:ns2="urn:uddi-org:api_v3" xmlns:ns3="urn:uddi-org:sub_v3"
brief="false">
<ns3:subscriptionKey>uddi:juddi.apache.org:8835aeec-c36f-4609-a131-d7f4769509d3</ns3:subscriptionKey>
<ns3:subscriptionFilter>
<ns2:find_service>
<ns2:name xml:lang="">%</ns2:name>
</ns2:find_service>
</ns3:subscriptionFilter>
<ns3:expiresAfter>2014-05-02T07:27:43.671-04:00</ns3:expiresAfter>
</subscription>
> Subscription API does not validate on saveSubscription
> ------------------------------------------------------
>
> Key: JUDDI-606
> URL: https://issues.apache.org/jira/browse/JUDDI-606
> Project: jUDDI
> Issue Type: Bug
> Affects Versions: 3.1.4
> Reporter: Alex O'Ree
> Assignee: Kurt T Stam
>
> This is OK with the subscription API. Note the empty business key. The
> subscription API should validate on all specific time subscriptions that the
> specified keys do in fact exist.
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <subscription xmlns:ns2="urn:uddi-org:api_v3" xmlns:ns3="urn:uddi-org:sub_v3"
> brief="false">
>
> <ns3:subscriptionKey>uddi:juddi.apache.org:85ad8319-fa23-400a-bcb6-37c439c5cd0f</ns3:subscriptionKey>
> <ns3:subscriptionFilter>
> <ns2:get_businessDetail>
> <ns2:businessKey></ns2:businessKey>
> </ns2:get_businessDetail>
> </ns3:subscriptionFilter>
> <ns3:expiresAfter>2014-05-01T07:15:01.865-04:00</ns3:expiresAfter>
> </subscription>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
