ebxml-msg message

Subject: [OASIS Issue Tracker] Created: (EBXMLMSG-27) EBMS Errors EBMS:0009 and EBMS:0010 have confusingly similar descriptions

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: ebxml-msg@lists.oasis-open.org
Date: Wed, 25 Sep 2013 10:54:40 +0000 (UTC)

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