Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When creating a subscription for asynchronous callbacks and NOT specifying a duration for updates, jUDDI accepts the save_subscription request. However after the subscription is made and trigger, the jUDDI server log outputs the following and the notification is NOT made.
Apr 22, 2013 8:47:02 PM org.apache.juddi.subscription.SubscriptionNotifier run
SEVERE: Could not obtain subscriptionResult for subscriptionKey uddi:juddi.apache.org:a603ca64-aa1c-41d9-bf5a-3b89ace54a65. null
java.lang.NullPointerException
at org.apache.juddi.subscription.SubscriptionNotifier.buildGetSubscriptionResults(SubscriptionNotifier.java:220)
at org.apache.juddi.subscription.SubscriptionNotifier.run(SubscriptionNotifier.java:152)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
From the spec
notificationInterval: This optional argument is only required when asynchronous notifications are used. It is of type xsd:duration and specifies how often change notifications are to be provided to a subscriber. If the notificationInterval specified is not acceptable due to node policy, then the node adjusts the value to match the next longer time period that is supported.
To fix, the subscription api should determine if a bindingkey is specified (or email address) AND a duration is null, throw an exception