I can understand your desire to see this for your immediate purposes, but
this solution is counter productive when you integrate AXIS into a
production environment or product.
If you prefer, I would be happy to enable DEBUG output to an "axis.log"
file, but not to the screen (Rich, who sits some 3 feet behind me, will
likely whack the back of my head if I start dumping such lines to the
console).
I think the pattern that seems most innocuous is to be notified of the
error on the console, and dig through the log for the details. If the
community has another opinion then I think it should be debated as a
"design point", rather than tweeking individual lines to help.
<ras>
*******************************************
Richard A. Sitze [EMAIL PROTECTED]
CORBA Interoperability & WebServices
IBM WebSphere Development
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
03/12/2002 03:00 cc:
PM Subject: cvs commit:
xml-axis/java/samples/stock
Please respond GetQuote.java
to axis-dev
dug 02/03/12 13:00:34
Modified: java/samples/stock GetQuote.java
Log:
Make error message go to the screen instead of some mystery log file
that newbies will never find.
Revision Changes Path
1.38 +1 -1 xml-axis/java/samples/stock/GetQuote.java
Index: GetQuote.java
===================================================================
RCS file: /home/cvs/xml-axis/java/samples/stock/GetQuote.java,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- GetQuote.java 8 Feb 2002 22:14:11 -0000 1.37
+++ GetQuote.java 12 Mar 2002 21:00:34 -0000 1.38
@@ -138,7 +138,7 @@
}
catch( Exception e ) {
if ( e instanceof AxisFault ) {
- ((AxisFault)e).dump();
+ System.err.println( ((AxisFault)e).dumpToString() );
} else
e.printStackTrace();
}
