Woo hoo !!
It's taken us one year and five months to fix this one !
A little self-congratulations is in order to have pulled this off at all - it was never going to be easy! Well done especially to Adrian and Samisa who have worked sooooo hard on this.
----- Forwarded by John Hawkins/UK/IBM on 14/02/2006 15:44 -----
| "Adrian Dick (JIRA)"
<axis-c-dev@ws.apache.org>
14/02/2006 14:52
|
|
[ http://issues.apache.org/jira/browse/AXISCPP-149?page=all ]
Adrian Dick resolved AXISCPP-149:
---------------------------------
Resolution: Fixed
I believe this piece of work to now be complete.
Based on the testcases available, this is working for client and server, for both doc/literal and rpc/encoded.
Should anyone find any missed items, it would be useful to raise those as seperate JIRA issues to aid tracking - as this issue ended up being a huge catch-all for memory related problems.
> 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
