Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <1099467789.1092306739778.JavaMail.apache@nagoya>
Date: Thu, 12 Aug 2004 03:32:19 -0700 (PDT)
From: axis-c-dev@ws.apache.org
To: axis-c-dev@ws.apache.org
Subject: [jira] Created: (AXISCPP-126) MemoryBlock handling issues in the
 maipulation of SOAP requets/responses
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
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: Unassigned
   Priority: Major

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

   Assignee: 
   Reporter: Fred Preston

    Created: Thu, 12 Aug 2004 3:32 AM
    Updated: Thu, 12 Aug 2004 3:32 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