[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-dev] Error Handling
I guess your "other team" is right i.e. errors/exceptions at business process level are conveyed to the other party by including business process specific error/exception documents in the ebXML Messages. The ebXML Messaging is neutral to whether it is used to carry a business document or a business exception. It's only the messaging level exceptions that make use of the ErrorList construct. thanks, Sanjay Patil ---------------------------------------------------------------------------------------------------------- IONA END 2 ANYWHERE Phone: 408 350 9619 http://www.iona.com -----Original Message----- From: Battenberg, Reinier [mailto:Reinier.Battenberg@mbcac.Mercedes-Benz.com] Sent: Wednesday, May 15, 2002 9:46 AM To: 'ebxml-dev@lists.ebxml.org' Subject: [ebxml-dev] Error Handling Hi, 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? Rgds, 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]
Powered by eList eXpress LLC