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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

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

Subject: RE: [ebxml-dev] Error Handling

IMO, the ebMS v1.0 spec contains an extension capability within the Error
element that allows developers to specify their own errorCodes.  Section contains a description of the codeContext attribute, where it states
the following:

"	codeContext attribute
The REQUIRED codeContext attribute identifies the namespace or scheme for
the errorCodes.  It MUST be a URI.  Its default value is
http://www.ebxml.org/messageServiceErrors.  If it does not have the default
value, then it indicates that an implementation of this specification has
used its own errorCodes.
Use of non-ebXML values for errorCodes is NOT RECOMMENDED.  In addition, an
implementation of this specification MUST NOT use its own errorCodes if an
existing errorCode as defined in this section has the same or very similar

I interpret this to mean you can use your own errorCodes within an Error
element "AS LONG AS":
 - the codeContext attribute identifies the namespace or scheme for the
- there is no equivalent or similar errorCode defined within ebXML for the
error you're reporting.

I use the codeContext attribute to identify the "error handler" to invoke in
order to properly process errors.

Dick Brooks
Systrends, Inc
7855 South River Parkway, Suite 111
Tempe, Arizona 85284
Web: www.systrends.com <http://www.systrends.com>

-----Original Message-----
From: Battenberg, Reinier
Sent: Wednesday, May 15, 2002 11:46 AM
To: 'ebxml-dev@lists.ebxml.org'
Subject: [ebxml-dev] Error Handling


We are implementing an ebXML 1.0 solution (only the messaging part of it),
and found out that two development teams interpreted the Error handling a
bit different. One team states that if an Error occurs inside one of the two
involved applications, you can use ebXML errorhandling (so it is allowed to
add an ErrorList in the reply), the other teams says that you can only use
the ErrorList if there is an error in the ebXML Message itself (ill
formatting, invalid values eg). If you want to do errorhandling of the
Business Process itself, you need to define your own errormessages and point
your Manifest towards them.

Who is right?


Reinier Battenberg
Senior IT Developer
Mercedes-Benz Customer Assistance Center N.V.
Maastricht, The Netherlands

The ebxml-dev list is sponsored by OASIS.
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.ebxml.org/ob/adm.pl>

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC