[ 
http://issues.apache.org/jira/browse/AXISCPP-860?page=comments#action_12356589 
] 

Dushshantha Chandradasa commented on AXISCPP-860:
-------------------------------------------------

This happens becourse the the following code of serialization in the generated 
complex type class.

bool blnIsNewPrefix = false;
        const AxisChar* sPrefix = pSZ->getNamespacePrefix(Axis_URI_attrlist, 
blnIsNewPrefix);
        if(blnIsNewPrefix)
                pSZ->serialize( " xmlns:", sPrefix , "=\"" , " 
http://complexlistservice.test.apache.org\"",0);
        pSZ->serialize( ">", 0);

the namespace is declared if it is new amespace. 

According to above logic, http://complexlistservice.test.apache.org is a 
previously declared namespace and its prefix is ns2. So the serializer does not 
declare it again. 

I introduces above condition to the serializer to avoid declaring the same 
namespace over and over again. It seems that this logic is not working. 

Any ideas on how we get rid of this bug??

> ComplexLists test is failing due to wrong request message
> ---------------------------------------------------------
>
>          Key: AXISCPP-860
>          URL: http://issues.apache.org/jira/browse/AXISCPP-860
>      Project: Axis-C++
>         Type: Bug
>   Components: Client - Engine
>     Reporter: James Jose
>     Assignee: nadir amra
>      Fix For: 1.6 Alpha

>
> Test fails because soap engine creates an element 'm_list_Ref' instead of 
> 'm_list'
> In the Request message generated for ComplexLists, one of the element name is 
> m_list_Ref. Earlier this element name was m_list and that time test was 
> passing. Now application server generates the following error message - 
> Cannot deserialize element m_list_Ref. 
> Request message - when test was passing
> ------------------------------------------------------------
> <?xml version='1.0' encoding='utf-8' ?>
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> <SOAP-ENV:Body>
> <ns1:multilist xmlns:ns1="http://complexlist.test.apache.org";>
> <ns1:arg_0_0><ns3:item 
> xmlns:ns3="http://complexlistservice.test.apache.org";>never odd or 
> even</ns3:item>
> <ns4:item xmlns:ns4="http://complexlistservice.test.apache.org";>any data 
> string</ns4:item>
> </ns1:arg_0_0>
> <ns1:arg_1_0><ns6:item 
> xmlns:ns6="http://complexlistservice.test.apache.org";><ns6:m_list><ns6:item>Apache</ns6:item>
> <ns6:item>Axis C++</ns6:item>
> </ns6:m_list><ns6:name>namepair1</ns6:name>
> </ns6:item><ns8:item 
> xmlns:ns8="http://complexlistservice.test.apache.org";><ns8:m_list><ns8:item>Test</ns8:item>
> <ns8:item>Complex</ns8:item>
> </ns8:m_list><ns8:name>namepair2</ns8:name>
> </ns8:item></ns1:arg_1_0>
> </ns1:multilist>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> Request Message : Now
> ----------------------------------
> <?xml version='1.0' encoding='utf-8' ?>
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> <SOAP-ENV:Body>
> <ns1:multilist xmlns:ns1="http://complexlist.test.apache.org";>
> <ns1:arg_0_0><ns3:item 
> xmlns:ns3="http://complexlistservice.test.apache.org";>never odd or 
> even</ns3:item>
> <ns4:item xmlns:ns4="http://complexlistservice.test.apache.org";>any data 
> string</ns4:item>
> </ns1:arg_0_0>
> <ns1:arg_1_0><ns6:item 
> xmlns:ns6="http://complexlistservice.test.apache.org";><ns6:m_list_Ref><ns6:item>Apache</ns6:item>
> <ns6:item>Axis C++</ns6:item>
> </ns6:m_list_Ref><ns6:name>namepair1</ns6:name>
> </ns6:item><ns8:item 
> xmlns:ns8="http://complexlistservice.test.apache.org";><ns8:m_list_Ref><ns8:item>Test</ns8:item>
> <ns8:item>Complex</ns8:item>
> </ns8:m_list_Ref><ns8:name>namepair2</ns8:name>
> </ns8:item></ns1:arg_1_0>
> </ns1:multilist>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
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

Reply via email to