jUDDI
  1. jUDDI
  2. JUDDI-591

Add support for email alerts for Subscription API

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.1.5
    • Component/s: None
    • Labels:
      None

      Description

      Referencing 5.5.8 save_subscription of the subscription API, (pist... Kurt said this part wasn't written)

      bindingKey: This optional argument of type anyURI specifies the bindingTemplate which the node is to use to deliver notifications to subscription listeners. It is only required when asynchronous notifications are used. This bindingTemplate MUST define either a Web service that implements notify_subscriptionListener (see below), or an email address to receive the notifications. If a notify_subscriptionListener Web service is identified, the node invokes it to deliver notifications. If an email address is identified, the node delivers notifications via email to the address supplied. When notifications are delivered via email, the body of the email contains the body of the SOAP message, which would have been sent to the notify_subscriptionListener service if that option had been chosen. The publisher making the subscription request MUST own the bindingTemplate. If this argument is not supplied, no notifications are sent, although subscribers may still use the get_subscriptionResults API to obtain subscription results. See Section 5.5.11 get_subscriptionResults for details. If email delivery to the specified address fails, nodes MAY attempt re-delivery, but are not obligated to do so. Depending upon node policy, excessive delivery failures MAY result in cancellation of the corresponding subscription.

      Service side changes, standard java mail api properties, plus delivery retry counts, reply email, maybe a pointer to a templated html stylized email

        Issue Links

          Activity

          Hide
          Alex O'Ree added a comment -

          Add sample configuration settings to the juddiv3.properties file

          Show
          Alex O'Ree added a comment - Add sample configuration settings to the juddiv3.properties file
          Hide
          Kurt T Stam added a comment -
          Show
          Kurt T Stam added a comment - Good point: https://github.com/KurtStam/juddi/wiki/GuideConfiguration Encryption is not directly supported by Commons Configuration AFAIK, we could add a GetEncryptedProperty - but I think this deserves its own jira. I will link it.
          Hide
          Alex O'Ree added a comment -

          Please document the location of where the mail server settings are suppose to be located and add sample settings within the juddiv3.properties files. In addition, if authentication is required, specify how we can store the password in an encrypted format

          Show
          Alex O'Ree added a comment - Please document the location of where the mail server settings are suppose to be located and add sample settings within the juddiv3.properties files. In addition, if authentication is required, specify how we can store the password in an encrypted format
          Hide
          Kurt T Stam added a comment -

          done by finishing the code that was there and adding a unit and integration test

          Show
          Kurt T Stam added a comment - done by finishing the code that was there and adding a unit and integration test
          Hide
          Kurt T Stam added a comment -

          I think the SMTP Notifiier is supposed to be doing this - but we're blocked by JUDDI-496 to load the appropriate binding. I test to make sure this works when 496 is fixed.

          Show
          Kurt T Stam added a comment - I think the SMTP Notifiier is supposed to be doing this - but we're blocked by JUDDI-496 to load the appropriate binding. I test to make sure this works when 496 is fixed.

            People

            • Assignee:
              Kurt T Stam
              Reporter:
              Alex O'Ree
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development