 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | Error Handling Strategy in an SOA | Error Handling Strategy in an SOA 2004-01-21 - By Vilayanur P. Krishnan
Back
Hi,
I am looking for best practices, patterns for handling errors (business
and system) in a service-oriented architecture. The requirements I'm
trying to address here are as follows:
* Participating services shall throw a service exception
encapsulating the business / system error.
* Consumers could be UI-based that need to comply with I18N as
well as batch-oriented systems (could be COTS-based systems e.g. based
on SAP).
Here are some of my questions:
* Should the services return error codes that then gets resolved
into a message and possibly even internationalized by the consumer
service? Each consumer would need to be aware of all possible error
codes, messages and any associated parameters from the services.
* Should the responsibility for the management of error codes and
their translation be handled by a totally different service (some sort
of an Error Director) that is also I18N-aware? Overkill?
* Should each service in the SOA be responsible for I18N - in
other words upon error, the Service would return a fully I18N message
back to the consumer. This would require the Consumer to let the Service
know of its language preferences, though.
Any pointers to best practices / patterns would be much appreciated.
Thanks
vp
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1226" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN
class=843385016-21012004>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=843385016-21012004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=843385016-21012004>I am looking for
best practices, patterns for handling errors (business and system) in a
service-oriented architecture. The requirements I'm trying to address here
are as follows: </SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=843385016-21012004></SPAN></FONT> </DIV>
<UL>
<LI><SPAN class=843385016-21012004><FONT face=Arial><FONT size=2><SPAN
class=325432019-21012004>Participating s</SPAN>ervices<SPAN
class=325432019-21012004> shall </SPAN>throw a service exception
encapsulating
the business / system error. </FONT></FONT></SPAN></LI>
<LI><SPAN class=843385016-21012004><FONT><FONT face=Arial><FONT size=2><SPAN
class=325432019-21012004>C</SPAN>onsumers could be UI-based that need to
comply with I18N as well as batch-oriented systems (could be COTS-based
systems e.g. based on SAP). </FONT></FONT></FONT></SPAN></LI></UL>
<DIV><SPAN class=843385016-21012004><FONT><FONT face=Arial size=2><SPAN
class=325432019-21012004>Here are some of my
questions:</SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=843385016-21012004><FONT><FONT face=Arial size=2><SPAN
class=325432019-21012004></SPAN></FONT></FONT></SPAN> </DIV>
<UL>
<LI><SPAN class=843385016-21012004><FONT><FONT face=Arial size=2><SPAN
class=325432019-21012004>Should the services return error codes that then
gets
resolved into a message and possibly even internationalized by the consumer
service? Each consumer would need to be aware of all possible error codes,
messages and any associated parameters from the
services.</SPAN></FONT></FONT></SPAN></LI>
<LI><SPAN class=843385016-21012004><FONT><FONT face=Arial size=2><SPAN
class=325432019-21012004>Should the responsibility for the management of
error
codes and their translation be handled by a totally different service (some
sort of an Error Director) that is also I18N-aware?
Overkill?</SPAN></FONT></FONT></SPAN></LI>
<LI><SPAN class=843385016-21012004><FONT><FONT face=Arial size=2><SPAN
class=325432019-21012004>Should each service in the SOA be responsible for
I18N - in other words upon error, the Service would return a fully I18N
message back to the consumer. This would require the Consumer to let the
Service know of its language preferences,
though.</SPAN></FONT></FONT></SPAN></LI></UL>
<DIV><FONT face=Arial size=2><SPAN class=843385016-21012004>Any
pointers <SPAN class=325432019-21012004>to best practices / patterns
</SPAN>would be much appreciated.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=843385016-21012004></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=843385016-21012004>Thanks</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=843385016-21012004>vp</SPAN></FONT></DIV></BODY></HTML>
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
