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 "Adrian Dick (JIRA)" <ax...@ws.apache.org> on 2005/12/07 10:14:12 UTC
[jira] Commented: (AXISCPP-149) Memory cleaning of generated C++ array code
[ http://issues.apache.org/jira/browse/AXISCPP-149?page=comments#action_12359558 ]
Adrian Dick commented on AXISCPP-149:
-------------------------------------
I have made a number of modifications to the API and internal implementation to more neatly handle memory cleaning of arrays.
The WSDL2Ws tooling has also been updated to reflect these changes, and also include a number of changes for the correct memory cleaning of other objects passed between the application and the axis engine.
At this time the WSDL2Ws changes are complete for client-side doc/literal generated stubs. Server-side and rpc/encoded changes are still being applied.
> Memory cleaning of generated C++ array code
> -------------------------------------------
>
> Key: AXISCPP-149
> URL: http://issues.apache.org/jira/browse/AXISCPP-149
> Project: Axis-C++
> Type: Improvement
> Components: WSDL processing - RPC
> Versions: 1.3 Final
> Environment: All Platforms
> Reporter: Samisa Abeysinghe
> Assignee: Adrian Dick
> Fix For: 1.6 Alpha
>
> 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.
--
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
Re: [jira] Commented: (AXISCPP-149) Memory cleaning of generated C++ array
code
Posted by Nadir Amra <am...@us.ibm.com>.
Adrian, I am just wondering whether this affected any of the external
APIs. I understand if this could not be helped, but it would be nice to
know what APIs or classes have changed.
Nadir K. Amra
"Adrian Dick (JIRA)" <ax...@ws.apache.org> wrote on 12/07/2005
03:14:12 AM:
> [ http://issues.apache.org/jira/browse/AXISCPP-149?
> page=comments#action_12359558 ]
>
> Adrian Dick commented on AXISCPP-149:
> -------------------------------------
>
> I have made a number of modifications to the API and internal
> implementation to more neatly handle memory cleaning of arrays.
>
> The WSDL2Ws tooling has also been updated to reflect these changes,
> and also include a number of changes for the correct memory cleaning
> of other objects passed between the application and the axis engine.
>
> At this time the WSDL2Ws changes are complete for client-side
> doc/literal generated stubs. Server-side and rpc/encoded changes
> are still being applied.
>
> > Memory cleaning of generated C++ array code
> > -------------------------------------------
> >
> > Key: AXISCPP-149
> > URL: http://issues.apache.org/jira/browse/AXISCPP-149
> > Project: Axis-C++
> > Type: Improvement
> > Components: WSDL processing - RPC
> > Versions: 1.3 Final
> > Environment: All Platforms
> > Reporter: Samisa Abeysinghe
> > Assignee: Adrian Dick
> > Fix For: 1.6 Alpha
>