Details
-
Type:
New Feature
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.5.1
-
Fix Version/s: 4.0.0
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
Nowadays, that the Petals BC Mail provided is not enough:
* it provides a generic service for which the service consumer must set all needed parameters: subject, body, addresses and mail server information. With this generic service, the service consumer can customize mail subject, body and addresses, * it provides a mode '{{static}}' where all parameters are set in the SU JBI descriptor. It's very good for mail server. But mail subject, body and addresses can not be customized by the service consumer information So it is needed to improve this component to introduce a mode '{{service}}' using annotations in WSDL. Following information can be extracted from the incoming payload as explained: * mail subject, defined as a {{Sting}} containing XPath placeholders that are evaluated at runtime, * mail body: ** defined as a {{Sting}} containing XPath placeholders that are evaluated at runtime, ** or, defined through an embedded XSL, ** or, defined from an embedded temaplte containing XPath placeholders that are evaluated at runtime, * target addresses ('to'), defined through an XPath expression returning a liste of {{Node}}, * flags to enable delivery status notification, and to defined the notification content. |
Nowadays, that the Petals BC Mail provided is not enough:
* it provides a generic service for which the service consumer must set all needed parameters: subject, body, addresses and mail server information. With this generic service, the service consumer can customize mail subject, body and addresses, * it provides a mode '{{static}}' where all parameters are set in the SU JBI descriptor. It's very good for mail server. But mail subject, body and addresses can not be customized by the service consumer information So it is needed to improve this component to introduce a mode '{{service}}' using annotations in WSDL. Following information can be extracted from the incoming payload as explained: * mail subject, defined as a {{String}} containing XPath placeholders that are evaluated at runtime, * mail body: ** defined as a {{Sting}} containing XPath placeholders that are evaluated at runtime, ** or, defined through an embedded XSL, ** or, defined from an embedded temaplte containing XPath placeholders that are evaluated at runtime, * target addresses ('to'), defined through an XPath expression returning a liste of {{Node}}, * flags to enable delivery status notification, and to defined the notification content. |
| Fix Version/s | 4.0.0 [ 10681 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
Nowadays, that the Petals BC Mail provided is not enough:
* it provides a generic service for which the service consumer must set all needed parameters: subject, body, addresses and mail server information. With this generic service, the service consumer can customize mail subject, body and addresses, * it provides a mode '{{static}}' where all parameters are set in the SU JBI descriptor. It's very good for mail server. But mail subject, body and addresses can not be customized by the service consumer information So it is needed to improve this component to introduce a mode '{{service}}' using annotations in WSDL. Following information can be extracted from the incoming payload as explained: * mail subject, defined as a {{String}} containing XPath placeholders that are evaluated at runtime, * mail body: ** defined as a {{Sting}} containing XPath placeholders that are evaluated at runtime, ** or, defined through an embedded XSL, ** or, defined from an embedded temaplte containing XPath placeholders that are evaluated at runtime, * target addresses ('to'), defined through an XPath expression returning a liste of {{Node}}, * flags to enable delivery status notification, and to defined the notification content. |
Nowadays, that the Petals BC Mail provided is not enough:
* it provides a generic service for which the service consumer must set all needed parameters: subject, body, addresses and mail server information. With this generic service, the service consumer can customize mail subject, body and addresses, * it provides a mode '{{static}}' where all parameters are set in the SU JBI descriptor. It's very good for mail server. But mail subject, body and addresses can not be customized by the service consumer information So it is needed to improve this component to introduce a mode '{{service}}' using annotations in WSDL. Following information can be extracted from the incoming payload as explained: * mail subject, defined as a {{String}} containing XPath placeholders that are evaluated at runtime, * mail body: ** defined as a {{Sting}} containing XPath placeholders that are evaluated at runtime, ** or, defined through an embedded XSL, ** or, defined from an embedded template containing XPath placeholders that are evaluated at runtime, * target addresses ('to'), defined through an XPath expression returning a liste of {{Node}}, * mail headers: ** with a header name defined as a constant, ** and a value defined as a {{Sting}} containing XPath placeholders that are evaluated at runtime, * flags to enable delivery status notification, and to defined the notification content. |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |