You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@axis.apache.org by "Mark Whitlock (JIRA)" <ax...@ws.apache.org> on 2005/02/24 16:10:51 UTC

[jira] Assigned: (AXISCPP-477) Inconsistent call::uninitialize when throwing faults from stubs

     [ http://issues.apache.org/jira/browse/AXISCPP-477?page=history ]

Mark Whitlock reassigned AXISCPP-477:
-------------------------------------

    Assign To: Mark Whitlock

> Inconsistent call::uninitialize when throwing faults from stubs
> ---------------------------------------------------------------
>
>          Key: AXISCPP-477
>          URL: http://issues.apache.org/jira/browse/AXISCPP-477
>      Project: Axis-C++
>         Type: Bug
>   Components: Client - Stub
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock

>
> When the generated stub catches AxisException (in FaultMappingTest for example) it throws exceptions back to the client application. Sometimes it calls Call::uninitialize before it throws the exception back and sometimes it doesn't. This looks wrong to me. Surely the call object should always be uninitialized before any exception is thrown back to the client application. This may not be a simple fix since uninitializing the call object may cause problems at termination when throwing some exceptions back.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira