[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EBXMLMSG-120) ebMS3 Core section 6.3, presence of RefToMessageId in errors
Pim van der Eijk created EBXMLMSG-120: ----------------------------------------- Summary: ebMS3 Core section 6.3, presence of RefToMessageId in errors Key: EBXMLMSG-120 URL: https://issues.oasis-open.org/browse/EBXMLMSG-120 Project: OASIS ebXML Messaging Services TC Issue Type: Improvement Components: Core Spec Reporter: Pim van der Eijk Section 6.3 states: _When reported as messages, ebMS Errors are packaged as ebMS Signal Messages. Several eb:ErrorÂelements MAY be present under eb:SignalMessage. If this is the case, and if eb:RefToMessageId isÂpresent as a child of eb:SignalMessage/eb:MessageInfo, then every eb:Error element MUST be relatedÂto the ebMS message (message-in-error) identified by eb:RefToMessageId._ _If the element eb:SignalMessage/eb:MessageInfo does not contain eb:RefToMessageId, then theÂeb:Error element(s) MUST NOT be related to a particular ebMS message.For an example of an ebXML Error Message, see Section 5.3.3._ This section is hard to read (second has an implication between two negated propositions). Â -- This message was sent by Atlassian JIRA (v7.7.2#77003)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]