Not sure what that means but if it means changing the default logging
level, I doubt that is the right solution since that will inevitably hide
current (expected) output.
-Dug
Richard Sitze/Austin/IBM@IBMUS on 10/22/2002 07:11:26 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: DO NOT REPLY [Bug 13845] - Axis logs/prints and
exception when it shouldn't
(bugzilla down...)
Don't forget about our "enterprise" level logging. It's not clear to me
that this particular situation applies.. but it's out there if it does.
<ras>
*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development
[EMAIL PROTECTED]
10/22/2002 01:46 PM
Please respond to axis-dev
To: [EMAIL PROTECTED]
cc:
Subject: DO NOT REPLY [Bug 13845] - Axis logs/prints
and exception when it shouldn't
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13845>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13845
Axis logs/prints and exception when it shouldn't
------- Additional Comments From [EMAIL PROTECTED] 2002-10-22 18:46
-------
We are going to have to distinguish genuine method raised faults from
unexpected
something-went-wrong with the invocation faults, then.
How do you propose we do this?
