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 "Dushshantha Chandradasa (JIRA)" <ax...@ws.apache.org> on 2005/03/07 05:02:52 UTC
[jira] Updated: (AXISCPP-342) There are too many leaks and possibilities for leaks in Param class and ParamValue class
[ http://issues.apache.org/jira/browse/AXISCPP-342?page=history ]
Dushshantha Chandradasa updated AXISCPP-342:
--------------------------------------------
Attachment: Param.DIFF
Made some modifications to Param.cpp and Param.h files regarding the above issue.Added a constructor, copy constructor and an overloaded assignment operator to ParamValue class.
> There are too many leaks and possibilities for leaks in Param class and ParamValue class
> ----------------------------------------------------------------------------------------
>
> Key: AXISCPP-342
> URL: http://issues.apache.org/jira/browse/AXISCPP-342
> Project: Axis-C++
> Type: Bug
> Components: Serialization
> Versions: 1.4 Final
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Assignee: Samisa Abeysinghe
> Fix For: 1.5 Alpha
> Attachments: Param.DIFF
>
> There are too many leaks in the class Param and the associated class ParamValue.
> As these are not documented (specially the couplings/dependancies) it is time consuming to fix them.
> Cleaning up members of ParamValue class is done by Param class - this is *VERY* bad - as it is difficult to track what has been release and what not.
> As a solution, need to make the class ParamValue a class of its own with destructor, constructor, copy constructor and assignment operator.
> Param class should need only worry about its own members.
> These leaks become apparent when there are exceptions with complex detail objects - I used tests/client/fault_mapping to track those.
--
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