OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (EBXMLMSG-107) Extensibility of ebMS3 error codes

    [ https://issues.oasis-open.org/browse/EBXMLMSG-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66832#comment-66832 ] 

Theo Kramer commented on EBXMLMSG-107:

The proposed change to the wording for 6.4.1 should clarify 'Adding new ebMS Errors' so I am in favor.

> Extensibility of ebMS3 error codes
> ----------------------------------
>                 Key: EBXMLMSG-107
>                 URL: https://issues.oasis-open.org/browse/EBXMLMSG-107
>             Project: OASIS ebXML Messaging Services TC
>          Issue Type: Improvement
>          Components: Core Spec
>            Reporter: Pim van der Eijk
> Section 6.4.1. of the Core Specification states the "ebMS Errors in addition to those specified here may be added by creating new errorCode values. The value of the errorCode attribute must begin with the five characters "EBMS:". "
> It is not cleaar who may add these error codes.  One obvious audience are specification authors,  and the Part 2 and AS4 specifications define additional errors.  However,  it is not explicitly stated that there errors are not to be used by implementers.  It would be undesirable if vendors start using other EBMS:* codes with proprietary semantics.   EBMS:0004 is a catch-all error, and there is ErrorDetails in which they can put any sub-codes or other additional information. 

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]