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 ax...@ws.apache.org on 2004/08/27 12:07:20 UTC

[jira] Resolved: (AXISCPP-126) MemoryBlock handling issues in the maipulation of SOAP requets/responses

Message:

   The following issue has been resolved as FIXED.

   Resolver: Roshan Weerasuriya
       Date: Fri, 27 Aug 2004 3:06 AM

The handler writer can use the "fini" method to do the memory clean up, such as to remove the HeaderBlocks etc. Note : A user shoudl not delete the Children and Attributes of a HeaderBlock, because they are automaticaly deleted by the Destructor of a HeaderBlock.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-126

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-126
    Summary: MemoryBlock handling issues in the maipulation of SOAP requets/responses
       Type: Bug

     Status: Resolved
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
 Components: 
             Basic Architecture
   Fix Fors:
             current (nightly)
   Versions:
             current (nightly)

   Assignee: Roshan Weerasuriya
   Reporter: Fred Preston

    Created: Thu, 12 Aug 2004 3:32 AM
    Updated: Fri, 27 Aug 2004 3:06 AM
Environment: n/a

Description:
The handler must be responsible for the de-allocation of HeaderBlocks, BasicNodes and Attributes that it has created, but there does not appear to be any mechanism in the Handler (either independently or on the destructor) for this.


---------------------------------------------------------------------
JIRA INFORMATION:
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