I've been debating doing this. My plan was to use the configurable
debug-installation flag and if it is not true (it defaults to 'production'
BTW, then stripping out the stack trace info right at the last minute, in
the AxisServlet itself). This would put it at a higher level than handlers.


...your tactic looks cleaner, but indicates that there are incomplete bits
in the Axis implementation...


----- Original Message -----
From: "Coffel, Kent" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 22, 2002 11:41 AM
Subject: stack trace in onFault()


I need to eliminate stack-traces and other implementation specific info when
a fault is encountered.  If my implementation throws an AxisFault, I can
control this.  But if an exception occurs at the global or transport layers
(e.g. client requested a non-existent service) I cannot seem to modify the
soap response.  I've tried registering custom handlers in at the global and
transport sections of server-config.wsdd and their invokes get called but
onFault() never does.  How can I modify this behavior so the response XML
does not include the stack trace and references to apache/axis?




Reply via email to