You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Alex O'Ree (JIRA)" <ju...@ws.apache.org> on 2013/04/23 02:57:17 UTC

[jira] [Created] (JUDDI-595) Subscription API NPE, Validation required

Alex O'Ree created JUDDI-595:
--------------------------------

             Summary: Subscription API NPE, Validation required
                 Key: JUDDI-595
                 URL: https://issues.apache.org/jira/browse/JUDDI-595
             Project: jUDDI
          Issue Type: Bug
            Reporter: Alex O'Ree
            Assignee: Kurt T Stam


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

--
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