[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ebxml-msg] EBMS0005 and EBMS0301
I’d agree with Sander here. For the Missing Receipt error, we should atleast have delivered or gotten a 200/201. I think our implementation gives a EBMS0005 today for connection failures.
From: "firstname.lastname@example.org" on behalf of Pim van der Eijk
Date: Monday, August 17, 2015 at 1:57 PM
Subject: Fwd: Re: [ebxml-msg] EBMS0005 and EBMS0301
-------- Forwarded Message --------
actually I think it does not matter much which of those errors is reported as both indicate failure of message delivery. I would say this is implementation specific. For the MissingReceipt error I can imagine that someone expects that the message is at least sent once to the receiving MSH and that the sending MSH is waiting for a receipt. So it could be a recommendation that this error is only generated after a successful send operation on the http level.
Reporting both errors is the most clearly indication of what happened.
But as said I would leave it up to the implementations to decide which error(s) to generate and report.