OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (EBXMLMSG-10) Unclear wording in App. E on reporting Security and Reliability errors

    [ http://tools.oasis-open.org/issues/browse/EBXMLMSG-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33685#action_33685 ] 

Jacques Durand  commented on EBXMLMSG-10:

Because the Reliability and Security modules are generally pipe-lined in front of the "ebMS packaging" module (see section 4.1) then SOAP Faults originating in these modules - say on the Receiver side - may be reported back to the Sender without being processed at all by the ebMS module on the Receiver side, and unbeknown from it,  i.e. just as SOAP Faults, not as ebMS Errors. In this category will be SOAP RM headers or Security headers that are not well-formed.
This is the situation where the footnote p.101 is alluding to.
The note should be understood as "A SOAP Fault generated by the Security or Reliability module is NOT required to be packaged as an ebMS error message."

Now, conversely, some ebMS Errors are "originating"  in the Security or Reliability modules, in the sense they reflect on a problem with the reliability or security function, that did not necessarily result in a SOAP Fault generation. This is the case of DeliveryFailure EBMS:0202: The Receiver reliability module simply failed to send back expected Acks, and that prompted the Sending reliability module to notify the Sending ebMS module to generated this ebMS Error (e.g. reported to its own application layer).. Similarly, DysfunctionalReliability EBMS:0201may be generated on the Sender side, if the Receiver reliability module is simply not responsive - e.g. refusing to create a reliable sequence, or to send back any Ack at all. So all the ebMS Errors in 6.7.2 and 6.7.3 should not be seen resulting from SOAP Faults.  They may sometimes, but even so their "reporting" can still be done in other ways than a bundled ebMS Error as indicated in 6.6.. 

> Unclear wording in App. E on reporting Security and Reliability errors
> ----------------------------------------------------------------------
>                 Key: EBXMLMSG-10
>                 URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-10
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Bug
>          Components: Core Spec
>            Reporter: Sander Fieten
>            Priority: Minor
> Footnote a on page 101 says that "This [SOAP] Fault is combined with an ebMS error message (eb:Messaging/eb:SignalMessage/eb:Error) unless it is generated by the Security or Reliability module."  
> This suggest that errors that occur in the Security or Reliability module will not be reported by an ebMS error message. Sections 6.7.2 and 6.7.3 however specify specific ebMS errors for these modules. 
> So the last part of the footnote, starting with unless is in conflict with the main text. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]