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/10/18 09:00:51 UTC
[jira] Updated: (AXISCPP-149) Memory cleaning of generated C++ array code
The following issue has been updated:
Updater: Samisa Abeysinghe (mailto:samisa_abeysinghe@yahoo.com)
Date: Sun, 17 Oct 2004 11:58 PM
Comment:
I guess this could be part of proposed WSDL2Ws tool refactoring for 1.4.
One thing to note is that using a class here would disable C support (this is why this was not fixed for 1.3)
Need to analyze how C support to be put back in place in 1.5 would be affected by the fix done for this issue.
Changes:
Version changed to 1.3 Final
Version changed from current (nightly)
Fix Version changed to 1.4 Alpha
Fix Version changed from 1.3 Beta
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXISCPP-149?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXISCPP-149
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXISCPP-149
Summary: Memory cleaning of generated C++ array code
Type: Improvement
Status: Open
Priority: Major
Project: Axis-C++
Components:
WSDL processing
Fix Fors:
1.4 Alpha
Versions:
1.3 Final
Assignee: Samisa Abeysinghe
Reporter: Samisa Abeysinghe
Created: Thu, 2 Sep 2004 8:02 PM
Updated: Sun, 17 Oct 2004 11:58 PM
Environment: All Platforms
Description:
In case of Arrays, I noticed that the WSDL2WS tool is generating a
struct.
e.g.
typedef struct SOAPStruct_ArrayTag
{
SOAPStruct* m_Array;
int m_Size;
} SOAPStruct_Array;
The trouble here is that in case of returned values/parameters the user
has to delete the m_Array mamber explicitly.
I think a more cleaner way would be to use a class here and use a
destructor to clean memory.
---------------------------------------------------------------------
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