[ http://issues.apache.org/jira/browse/AXISCPP-149?page=comments#action_12360287 ]
Dushshantha Chandradasa commented on AXISCPP-149:
-------------------------------------------------
Doc/lit server side is perfectly working with windows. Can test with InteropTestRound1Doc
test case. The service for this test is InreopBaseDoc.
In RPC, there is a deserialization problem. The deserializer returns a null array. It looks
to me as the deserializer cannot correctly handle the wrapper element of the array.
<ns1:echoStringArray xmlns:ns1="http://soapinterop.org/">
<inputStringArray xmlns:enc="http://www.w3.org/2001/06/soap-encoding" enc:arrayType="xsd:string[2]">
<item>0th element of string array</item>
<item>1th element of string array</item>
</inputStringArray>
</ns1:echoStringArray>
service fails to deserialize this part of the message.
> 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: Dushshantha Chandradasa
> 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
|