Forum Discussion
Kevin_Slade
14 years agoContributor
Further to above information, when array elements are deleted and then later recreated (eg DelayDataSource) the DelayDataSource section of the XML is generated immediately below the <Config> rather than below the <nin:DataSource> elements where it is expected.
The result of this is that the XML ordering is lost and the Axis2C soap server refuses to process the generated XML. Manually moving the out of order XML elements to to appropraite place allows the Axis2C server to process the request.
The result of this is that the XML ordering is lost and the Axis2C soap server refuses to process the generated XML. Manually moving the out of order XML elements to to appropraite place allows the Axis2C server to process the request.
<Config>
<nin:DelayDataSource>
<nin:DataObject>
<nin:Type>ROTFILE</nin:Type>
<nin:Name>rot_col3</nin:Name>
</nin:DataObject>
<nin:Delay>15</nin:Delay>
</nin:DelayDataSource>
<nin:DelayDataSource>
<nin:DataObject>
<nin:Type>ROTFILE</nin:Type>
<nin:Name>rot_col4</nin:Name>
</nin:DataObject>
<nin:Delay>20</nin:Delay>
</nin:DelayDataSource>
<nin:Enabled>false</nin:Enabled>
<!--0 or more repetitions:-->
<nin:DataSource>
<nin:Type>ROTFILE</nin:Type>
<nin:Name>rot_col1</nin:Name>
</nin:DataSource>
<!--Optional:-->
<nin:DataSource>
<nin:Type>ROTFILE</nin:Type>
<nin:Name>rot_col2</nin:Name>
</nin:DataSource>
<!-- The <nin:DelayDataSource> elements need to be inserted here -->
<nin:MergeSources>CONCURRENT</nin:MergeSources>
Related Content
- 10 months agosanket2799