[ http://issues.apache.org/jira/browse/AXISCPP-189?page=all ]
Adrian Dick closed AXISCPP-189:
-------------------------------
> Stub falls over after first stub has been deleted
> -------------------------------------------------
>
> Key: AXISCPP-189
> URL: http://issues.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://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|