I could be convinced that command-line tools should dump to stderr.
However, by logging we CAN capture the problem for review without
re-running a test.

Regardless, the internal AXIS runtime should always log and/or throw an
exception; it should NEVER write to stdout/stderr.  I recognize that at
somepoint there would be a benefit in reviewing all exeptions (thrown or
caught) and any associated logging.

See other note for possible solution....  turning on logging by default.
Integrators may wish to revisit the log4j properties file.
<ras>

*******************************************
Richard A. Sitze            [EMAIL PROTECTED]
CORBA Interoperability & WebServices
IBM WebSphere Development


                                                                                       
                 
                      Doug                                                             
                 
                      Davis/Raleigh/IB         To:      [EMAIL PROTECTED]        
                 
                      M@IBMUS                  cc:                                     
                 
                                               Subject: Re: cvs commit: 
xml-axis/java/samples/stock     
                      03/12/2002 03:09         GetQuote.java                           
                 
                      PM                                                               
                 
                      Please respond                                                   
                 
                      to axis-dev                                                      
                 
                                                                                       
                 
                                                                                       
                 




I'd like to raise this as an issue - not sure whether or not its worth
stopping the beta or not (probably not) but I do think that if this
is not fixed a lot of newbies will be very very confused.

Right now we seem to log almost everything.  This change is
an example of how something that should clearly go to stderr
was being sent to some mystery log file WHICH btw 3 commiters
of axis (I'll keep the other 2 people out of this - but they're "in the
know") could not figure out where the heck log message go.
So, I see two problems here:
1 - how can we expect newbies to figure it out when its such a mystery
    that axis developers themselves don't know (or at least not easily).
2 - we log too much.  Simple things like errors while running the
    AdminClient (from "main") are logged instead of being printed to
    the screen - which leaves cmd line people thinking it worked.
I really think the choice between logging and println's need to be
reexamined.  I think we've gone too far one direction.

-Dug

ps. this fixed my "issue #2" for the beta.



[EMAIL PROTECTED] on 03/12/2002 04:00:34 PM

Please respond to [EMAIL PROTECTED]

To:    [EMAIL PROTECTED]
cc:
Subject:    cvs commit: xml-axis/java/samples/stock GetQuote.java



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();
       }








Reply via email to