[jira] Resolved: (AXISCPP-189) Stub falls over after first stub has been deleted

["Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>]

     [ http://nagoya.apache.org/jira/browse/AXISCPP-189?page=history ]
     
Samisa Abeysinghe resolved AXISCPP-189:
---------------------------------------

     Resolution: Fixed
    Fix Version: 1.3 Final

The sample code attached works.
See previous comment for more details.

> Stub falls over after first stub has been deleted
> -------------------------------------------------
>
>          Key: AXISCPP-189
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-189
>      Project: Axis-C++
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.3 Final
>     Reporter: Mark Whitlock
>     Priority: Minor
>      Fix For: 1.3 Final
>  Attachments: AXISCPP-189.cpp
>
> The first Call to be created remembers that it issued initialize_module and issues uninitialize_module in its destructor. Other Call objects don't issue initialize_module. If other Call objects are used after the first Call has been deleted, uninitialize_module will have been called and they will fall over. There should be a reference count of the number of Call objects and the *last* one should issue uninitialize_module, not the one that issued initialize_module. This problem will happen for Stubs and generated stubs, since a generated stub has a Stub and a Stub has a Call.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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