• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 873
  • Last Modified:

xsi:nil and xsi:type attribute order in an element. Does it matter?

Hi,

I have a strange error with my integration platform (webMethods). When i send xsi:nil="true" in an element the element only gets parsed as null if xsi:nil="true" is the last attribute in the element.

I have made a small web service just to test it. It will print out the input after the integration platform have parsed it from xml to its internal format.
This is how the different request looks like, coupled with the printouts of the variable value (notice that the only change in the request is the middle row that I have put two lank rows around.).

Request 1:
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:jak="http://www.test.com/icc/tip/test/jakothun">
   <soapenv:Header/>
   <soapenv:Body>
      <jak:nillableTest soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
         <jakobTest.nillableTest.docs_x003A_myNillableTestDoc xsi:type="prin:__myNillableTestDoc" xmlns:prin="http://localhost/jakobTest/nillableTest/flow/printPayload">

            <optionalAndNotNull xsi:type="xsd:string" xsi:nil="true" />

         </jakobTest.nillableTest.docs_x003A_myNillableTestDoc>
      </jak:nillableTest>
   </soapenv:Body>
</soapenv:Envelope>

Answer1: (parsed value outputted to a log):
optionalAndNotNull = null

Request2:
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:jak="http://www.test.com/icc/tip/test/jakothun">
   <soapenv:Header/>
   <soapenv:Body>
      <jak:nillableTest soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
         <jakobTest.nillableTest.docs_x003A_myNillableTestDoc xsi:type="prin:__myNillableTestDoc" xmlns:prin="http://localhost/jakobTest/nillableTest/flow/printPayload">

            <optionalAndNotNull xsi:nil="true" xsi:type="xsd:string" />

         </jakobTest.nillableTest.docs_x003A_myNillableTestDoc>
      </jak:nillableTest>
   </soapenv:Body>
</soapenv:Envelope>

Answer2:
optionalAndNotNull = ''
(empty string with two ' around)

Now to the question. Is there any XML experts out here that know if the w3c XML standard specify anything about which order xsi:nil attributes must be specified to be correct and always parsed correctly by good xml tools?
Or is this just a silly bug in my integration platform, that I should report to them instead?
0
sawdustwilly
Asked:
sawdustwilly
1 Solution
 
Geert BormansInformation ArchitectCommented:
order of attributes should not be important in XML terms.
A set of attributes is an unordered nodeset
Any application that requires a specific attribute to be the last attribute in the row is erroneous
so you should report this to the integration platform vendor

cheers

Geert
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now