← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] (EBXMLMSG-4) 6.6 Error Reporting, SOAP Faults

From
OASIS Issues Tracker <>
Date
2014-05-07T08:12:56+00:00
ID
JIRA.20805.1359564382000.496.1399450386044@customer-jira
Thread
[OASIS Issue Tracker] (EBXMLMSG-4) 6.6 Error Reporting, SOAP Faults
[ https://tools.oasis-open.org/issues/browse/EBXMLMSG-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sander Fieten updated EBXMLMSG-4:
---------------------------------

    Proposal: 
Change last sentence of third bullet (line 2253 of PDF) to:
"The reporting message may be combined with a SOAP Fault."

Also mention the HTTP status codes that will be the result of the selected option which would be 500 for SOAP Fault sending and 20x for ebMS error sending (even when the ebMS error is combined with a SOAP Fault).

  was:
Change last sentence of third bullet (line 2253 of PDF) to:
"The reporting message may be combined with a SOAP Fault."

Also mention the HTTP status codes that will be the result of the selected option.


> 6.6 Error Reporting,  SOAP Faults
> ---------------------------------
>
>                 Key: EBXMLMSG-4
>                 URL: https://tools.oasis-open.org/issues/browse/EBXMLMSG-4
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: Core Spec
>            Reporter: Pim van der Eijk
>
> Section 6.6 describe the use of SOAP Faults with "failure" errors in a way that may not be compatible with the example in section 5.5.
> See discussion on https://lists.oasis-open.org/archives/ebxml-msg/201301/msg00020.html.  



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
← Prev in month ← Prev in thread
Next in thread → Next in month →