axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Whitlock (JIRA)" <>
Subject [jira] Closed: (AXISCPP-534) HTTPTransport::flushOutput should be declared throw(AxisException)
Date Wed, 16 Mar 2005 22:16:25 GMT
     [ ]
Mark Whitlock closed AXISCPP-534:

    Resolution: Fixed

I have updated HTTPTransport::flushOutput to throw(AxisException,HTTPTransportException).
Although the code does catch(...) { throw; } no exceptions are expected to be caught and rethrown
by this catch statement. It is worthwhile leaving this catch(...) statement in the code however,
since if ever a different exception was thrown it would be traced.

> HTTPTransport::flushOutput should be declared throw(AxisException)
> ------------------------------------------------------------------
>          Key: AXISCPP-534
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Transport (axis3)
>     Reporter: Tim Bartley
>     Assignee: Mark Whitlock
>     Priority: Minor

> HTTPTransport::flushOutput is declared throw(HTTPTransportException) however it has code
that rethrows AxisExceptions and unrecognized exceptions. Doing this will abort the process
since throwing exceptions that don't an exlict throw declaration are required to call the
"unexpected()" exception handler which aborts the process.
> Either flushOutput should be modified to map non HTTPTransportException's to HTTPTransportExceptions
or flushOutput should be redeclared to throw(AxisException) and modified to map (...) to an
> Cheers,
> Tim

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message