[jira] Commented: (AXISCPP-652) NilValuesTest failing

["Dushshantha Chandradasa (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXISCPP-652?page=comments#action_65592 ]
     
Dushshantha Chandradasa commented on AXISCPP-652:
-------------------------------------------------

I found the problem here. Here the elements in aRecord complex type are in a wsdl 'all' block.

  <xsd:complexType name="aRecord">
				<xsd:all>
					<xsd:element name="field1" type="xsd:string" nillable="true"/>
					<xsd:element name="field2" type="xsd:string" fixed="field2Value"/>
					<xsd:element name="field3" type="xsd:string" nillable="false"/>
				</xsd:all>
			</xsd:complexType>

According to our 'all' construct handling implementation, element is checked for NULL before it is serialized.

Here, the case is engine does not serialize the element because it is set to NULL. This is a bug in the 'all' construct handdling and chinthana will fix it as soon as possible. 

> NilValuesTest failing
> ---------------------
>
>          Key: AXISCPP-652
>          URL: http://issues.apache.org/jira/browse/AXISCPP-652
>      Project: Axis-C++
>         Type: Bug
>     Reporter: Adrian Dick

>
> The NilValuesTest has just started failing in the automated daily test run.
> The nillable entries are no longer present in the SOAP request:
> --snip--
>  <SOAP-ENV:Body>
>  <ns1:myOperation xmlns:ns1="http://complextype.test.apache.org">
>  <ns1:aType></ns1:aType>
>  </ns1:myOperation>
> --snip--
> For the purposes of this testcase the correct message must contain these element, with the attribute xsi:nil="true", as shown below:
> --snip--
>  <SOAP-ENV:Body>
>  <ns1:myOperation xmlns:ns1="http://complextype.test.apache.org">
>  <ns1:aType><ns1:field1 xsi:nil="true"></ns1:field1>
>  <ns1:field2 xsi:nil="true"></ns1:field2>
>  <ns1:field3 xsi:nil="true"></ns1:field3>
>  </ns1:aType>
>  </ns1:myOperation>
> --snip--
> Looking at the CVS change history between this test passing and failing, I have identified the following file changes in WSDL2Ws
> - taking a quick look it isn't clear to me if these are the direct cause of the problem, or whether the generated stubs are now using a slightly different API containing the problem.
> ws-axis/c/src/wsdl/org/apache/axis/wsdl/symbolTable/CElementDecl.java
> ws-axis/c/src/wsdl/org/apache/axis/wsdl/symbolTable/CSchemaUtils.java
> ws-axis/c/src/wsdl/org/apache/axis/wsdl/wsdl2ws/cpp/literal/BeanParamWriter.java
> ws-axis/c/src/wsdl/org/apache/axis/wsdl/wsdl2ws/info/AttributeInfo.java
> ws-axis/c/src/wsdl/org/apache/axis/wsdl/wsdl2ws/info/ElementInfo.java
> ws-axis/c/src/wsdl/org/apache/axis/wsdl/wsdl2ws/ParamWriter.java
> ws-axis/c/src/wsdl/org/apache/axis/wsdl/wsdl2ws/WSDL2Ws.java

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