Message
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@java.sun.com
