[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (EBXMLMSG-27) EBMS Errors EBMS:0009 and EBMS:0010 have confusingly similar descriptions
[ http://tools.oasis-open.org/issues/browse/EBXMLMSG-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Makesh Rao updated EBXMLMSG-27:
-------------------------------
Description:
The description for EBMS:0009 reads as follows
The ebMS header is either not well formed as an XML document, or does not conform to the ebMS packaging rules.
and for EBMS:0010 it reads as follows
The ebMS header or another header (e.g. reliability, security) expected by the MSH is not compatible with the expected content, based on the associated P-Mode.
This in particular for pull signal messages where the p-mode must be determined from the mpc, the UTs, and/or the X509 cert
was:
The description for EBMS:0009 reads as follows
The ebMS header is either not well formed as an XML document, or does not conform to the ebMS packaging rules.
and for EBMS:0010 it reads as follows
The ebMS header or another header (e.g. reliability, security) expected by the MSH is not compatible with the expected content, based on the associated P-Mode.
This in particular for pull signal messages where the p-mode must be determined from the mpc, the UTs, and/or the X509 cert
Proposal:
Reword the description for EBMS:0010 as follows
No p-mode could be determined for the received ebMS message"
Also change the Short Description to "ProcessingModeNotFound"
was:
Reword the description for EBMS:0010 as follows
No p-mode for the message received could be determined from the ebMS header, the pull request MPC, the UTs or the X509 certificate.
> EBMS Errors EBMS:0009 and EBMS:0010 have confusingly similar descriptions
> -------------------------------------------------------------------------
>
> Key: EBXMLMSG-27
> URL: http://tools.oasis-open.org/issues/browse/EBXMLMSG-27
> Project: OASIS ebXML Messaging Services TC
> Issue Type: Improvement
> Components: Core Spec
> Reporter: Theo Kramer
> Priority: Minor
>
> The description for EBMS:0009 reads as follows
> The ebMS header is either not well formed as an XML document, or does not conform to the ebMS packaging rules.
> and for EBMS:0010 it reads as follows
> The ebMS header or another header (e.g. reliability, security) expected by the MSH is not compatible with the expected content, based on the associated P-Mode.
> This in particular for pull signal messages where the p-mode must be determined from the mpc, the UTs, and/or the X509 cert
--
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]