[
https://issues.apache.org/jira/browse/JUDDI-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree updated JUDDI-591:
-----------------------------
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
was:
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
> Add support for email alerts for Subscription API
> -------------------------------------------------
>
> Key: JUDDI-591
> URL: https://issues.apache.org/jira/browse/JUDDI-591
> Project: jUDDI
> Issue Type: Bug
> Reporter: Alex O'Ree
> Assignee: Kurt T Stam
> Fix For: 3.1.5
>
>
> 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
--
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
