Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.1.4
-
None
-
None
Description
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>
Attachments
Issue Links
- blocks
-
JUDDI-579 Make a new end user web interface
- Closed
- is related to
-
JUDDI-595 Subscription API NPE, Validation required
- Closed
-
JUDDI-596 Subscription callback without a transport type is not delivered
- Closed
- relates to
-
JUDDI-242 Expand UDDI_090_SubscriptionListenerIntegrationTest to more elements
- Resolved