[Trustedjava-support] excessive e.printStackTrace

[Michael S. <ms...@nt...>]

Hi -

Buried in many of the soap side libraries are unconditional 
"e.printStackTrace()" calls.  Most, if not all, of these are debugging 
statements - but there's no way to keep them from popping up.  They 
occur even if I catch and discard the exception.   I even tried to 
redirect the output of System.err to the equivalent of /dev/null, but I 
still get popup error messages that come from the finalization process.

It would be nice if these were instead piped into the logging system, or 
made conditional (e.g. global replace e.printStackTrace() with 
JTssUtil.printStackTrace(e) and build a utility that looks at a 
properties value).

Mike