Distinguish client and server exceptions when calling XFireProxy
----------------------------------------------------------------
Key: XFIRE-361
URL: http://jira.codehaus.org/browse/XFIRE-361
Project: XFire
Type: Improvement
Components: Core
Versions: 1.0
Reporter: Fried Hoeben
Assigned to: Dan Diephouse
When making a call from a client to a server (via an XFireProxy) I would like
to distinguish the following cases (currently they all cause a
XFireRuntimeException wrapping an XFireFault):
1. problem calling the service (e.g. org.codehaus.xfire.fault.XFireFault:
Couldn't send message)
2. service was reached but threw an exception/fault (e.g.
org.codehaus.xfire.fault.XFireFault: Could not get JDBC Connection; nested
exception is org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create
PoolableConnectionFactory (Io exception: The Network Adapter could not
establish the connection))
Case 1 is a client configuration or network problem. I probably would want to
be able to get the service URL from the exception. (Since I'm a client calling
a proxy that information is not that easy to obtain.)
Case 2 is a problem inside the service or with my usage of it, I would probably
want to get the arguments passed to the service. (But this is not that
important, since I can easily get in my client code).
In neither case I mind that a runtime exception is thrown, but I would just
like to be able to differentiate, so maybe two different subclasses...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
