[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EBXMLMSG-67) Error to generate when P-Mode can not be determined
[ https://issues.oasis-open.org/browse/EBXMLMSG-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sander Fieten updated EBXMLMSG-67: ---------------------------------- Summary: Error to generate when P-Mode can not be determined (was: Error to generated when P-Mode can not be determined) > Error to generate when P-Mode can not be determined > --------------------------------------------------- > > Key: EBXMLMSG-67 > URL: https://issues.oasis-open.org/browse/EBXMLMSG-67 > Project: OASIS ebXML Messaging Services TC > Issue Type: Bug > Components: Core Spec > Reporter: Sander Fieten > > The current text of the specification is not very clear if an error should be generated when the P-Mode can not be determined for a received message. > Questions that arise are: > 1) Do we want to specify a specific Error for this situation? > 2) If so, which Error should be used? > Section 6.7.1 of the Core Spec lists the standard ebMS processing errors. Based on the short descriptions it seems logical that EBMS:0010 - ProcessingModeMismatch is the correct Error to return. However the description of the semantics - "the header expected by the MSH is not compatible with the expected content, based on the associated P-Mode." - is a bit unclear because of the incompatibility between expectations and that it talks about an associated P-Mode. Especially the latter seems to suggest that a P-Mode is found for the message. Another option could be Error EBMS:0001 - ValueNotRecognized as the MSH is unable to find the P-Mode based on the received information. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]