Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: 1 Apr 2004 11:28:05 -0000
Message-ID: <20040401112805.20671.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 28123] New:  -
    ClientAbortException should default to the description of the wrapped
 exception

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28123>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28123

ClientAbortException should default to the description of the wrapped exception

           Summary: ClientAbortException should default to the description
                    of the wrapped exception
           Product: Tomcat 5
           Version: 5.0.19
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: Joerg.Thoennes@macd.com


Browsing the source code, I have seen that the call

throw new ClientAbortException( e )

does store null as the message description. IMHO, the ClientAbortException
should store the result of e.getDescription() here if no own description is
given.

If some application component later prints

    ...
    } catch ( Exception e ) {
        log( "..." + e );
    }

there would be a "null" in the log instead of anything useful.

This would make the logging a little bit more useful.

Cheers, Jörg

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org