JSON Values null vs undefined and resulting xml output

[jamienich]

The xmlHandler equality operator "==" evaluates undefined and null values as true as follows:

xmlHandler.js, Lines 165-173

      if (val == null) {
        if (descriptor.isNillable) {
          // Set xsi:nil = true
          declareNamespace(nsContext, element, 'xsi', helper.namespaces.xsi);
          if (typeof element.attribute === 'function') {
            element.attribute('xsi:nil', true);
          }
        }
      }

It would be preferable to set the xsi:nil = true only for null values and not undefined values.
If we exclude undefined values from the block above undefined values are shown in the XML as follows:

<some_attribute/>

Suggest using the type safe equality operator so it only evaluates null as true:

      if (val === null) { 
        if (descriptor.isNillable) { 
          // Set xsi:nil = true
          declareNamespace(nsContext, element, 'xsi', helper.namespaces.xsi);
          if (typeof element.attribute === 'function') {
            element.attribute('xsi:nil', true);
          }
        }
      }

The new code allows strong-soap to set a xsi:nil=true when null is passed as a value or an empty XML tag.
Not sure how the empty XML tag would be passed otherwise.

Seems like a fairly major change if users are used to xsi:null=true being set if they pass through undefined currently, thoughts on this?

[jamienich]

Think I posted this in the wrong place, sorry.