You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2007/04/10 19:44:33 UTC
[jira] Resolved: (AXIS2-2496) JAX-WS Servicability Exception Issues
[ https://issues.apache.org/jira/browse/AXIS2-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-2496.
-----------------------------------
Resolution: Fixed
Revision 517217
> JAX-WS Servicability Exception Issues
> -------------------------------------
>
> Key: AXIS2-2496
> URL: https://issues.apache.org/jira/browse/AXIS2-2496
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assigned To: Rich Scheuerle
>
> During testing, we identified two servicability issues related to exception flow.
> 1) All WebService exceptions flow through the ExceptionFactory. During this processing, we do root cause analysis to determine the root cause of the exception.
> This information is ultimately flowed back to the client in a soap fault. However we did not have adequate logging to detect where the root cause exception occurred. This
> is now added.
> 2) If the customer's web service throws an exception, the web service runtime intercepts the exception and builds the appropriate service or system fault. Like (1) we fail
> to adequately log the where (in the stack) the exception occurred.
> I will be adding this additional serviceability code in the next few minutes after I complete testing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org