You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is actually the result of a bug that could also cause crashes if tag children exist before attributes. This should now be fixed in dev (and the automatically generated snapshot release).
We have the following configuration for the XML parser:
nilAttribute = qname(Namespaces.XmlSchemaInstance, "nil", Prefixes.XmlSchemaInstance) to "true"
When we serialize a class the order of the element is not preserved when an element is null:
<Parameters> <IgnoreLimitWarningsArray xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> <ExecutionInstructionsArray xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> <ExecutionInstructionsDictionaryArray xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> <ExecutionInstructionsRestatedArray xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> <ClientSequenceNumberArray xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> <CustomColumnsArray xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> <CustomColumnsRestatedArray xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> <TradingPassword xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/> <OrderNumberArray> <OrderNumber>138084514</OrderNumber> </OrderNumberArray> </Parameters>
All the nil elements are placed at the top which is not the correct definition of sequence order:
`@Serializable
@XmlSerialName(value = "Parameters")
class OrderDelete (
@xmlelement
@XmlSerialName("OrderNumberArray")
@XmlChildrenName("OrderNumber", namespace = "http://webservices.iress.com.au/v4/")
val orderNumberArray: List,
)`
Unfortunately the SOAP service we are integrating to requires the order to be preserved. Is the away to fix this?
The text was updated successfully, but these errors were encountered: