Re: Excessive output by Axis

[btomasini]

My guess...

log4j.properties was embedded in the jar, seding info 
level to sysout.

This should not be the case.  Not sure if this is absent, 
as it should be, in the current jar.

Ben

On Thu, 4 Sep 2003 16:37:16 +0100
 "Andy Overton" <[EMAIL PROTECTED]> wrote:
I guess nobody knows!

It seems in version 1.1 this has been removed.  Still 
bemused as to why it
was in there in the first place though.
----- Original Message -----
From: "Andy Overton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 01, 2003 5:02 PM
Subject: Excessive output by Axis


Could anyone explain why when using Axis it outputs all 
AxisFaults to
standard out even if i catch them and on the server side 
whenever I throw
one?

My basic client code is :

        try
        {
            ....
            System.out.println("Making invalid call");
            call.invoke(new Object[] {new Integer(0), 
new Integer(0)});
        }
        catch(AxisFault af)
        {
            System.out.println("Axis Fault!");
            System.out.println("e.getFaultCode() = " + 
af.getFaultCode());
            System.out.println("e.getFaultString() = " +
af.getFaultString());
        }

and yet on the client side it outputs :

Making valid call
Making invalid call
20 [main] INFO axis.enterprise  - Mapping Exception to 
AxisFault
AxisFault
 faultCode: 
{http://xml.apache.org/axis/}Client.INVALID_SERVICE_TYPE
 faultString: Type was wrong
 faultActor: null
 faultDetail:
 stackTrace: AxisFault
 faultCode: 
{http://xml.apache.org/axis/}Server.generalException
 faultString:
 faultActor: null
 faultDetail:
.....
<snipped about 4 pages of stack trace>

Where is this output coming from? It appears to be 
logging but I have no
log4j.properties file and wouldn't expect it to log to 
screen anyway. It
also appears to be mapping some exception to an 
AxisFault but all the
server
returns is an AxisFault.

Also, on the server side in my Tomcat window i get the 
following even
though
my code outputs nothing. This means every error I get 
floods my Tomcat
window with pages upon pages of pointless stack trace i 
didn't ask for :

 addService called with service type : 0

- Exception:
AxisFault
 faultCode: 
{http://xml.apache.org/axis/}Client.INVALID_SERVICE_TYPE
 faultString: Type was wrong
 faultActor: null
 faultDetail:
        stackTrace: AxisFault
 faultCode: 
{http://xml.apache.org/axis/}Server.generalException
 faultString:
 faultActor: null
 faultDetail:

        at
com.qinetiq.tim.rvs.broker.BrokerException.&lt;init&gt;(BrokerExcepti
on.java:32)
...... (2 more pages worth of stack trace)
I can't find any explanation in the notes and i can't 
find anything in the
source, if anyone can shed any light on this or even 
better tell me how I
can switch it off i'd really appreciate it.

Andy Overton