#2711 LOCALNAMESPACEPATH allows 0 NAMESPACE children

[Dave Blaschke]

Both the DOM parser's parseLOCALNAMESPACEPATH and SAX parser's LocalNameSpacePathNode allow zero NAMESPACE children, using some default local namespace builder instead. This is against what has been defined in the spec since 1.0/2.0 (they are soon coming out with 1.4/2.4):

<!ELEMENT LOCALNAMESPACEPATH (NAMESPACE+)>

Although not documented in the code, there are probably some old CIMOMs that sent an empty LOCALNAMESPACEPATH element and let the client determine the local namespace path.

Because this is a violation of the CIM-XML specs BUT there may be CIMOMs out there that still do it, a property will be added (default to spec compliance) to allow the old behavior.

[Dave Blaschke]

Patch sent for community review. During a 2 week period any exploiter may comment on the patch, request changes or turn it down completely (with good reason). For the time being the patch is part of the "Experimental" branch in CVS.

[Dave Blaschke]

# If set to true, the CIM-XML parser will allow empty LOCALNAMESPACEPATH
# elements in incoming responses.  If set to false, the parser will not
# allow empty LOCALNAMESPACEPATH elements.
#
# Note: Some older CIMOMs sent empty LOCALNAMESPACEPATHs, relying on the
# client to provide the local namespace path.  This is a violation of
# DSP0201, which dictates that LOCALNAMESPACEPATH must contain at least
# one NAMESPACE child.  By default, this property is set to false so the
# client can adhere to the CIM-XML specifications.  Set this property to
# true if "LOCALNAMESPACEPATH requires NAMESPACE" exceptions occur while
# interacting with one of these older CIMOMs.
#
# Type: Boolean
# Recognition: Anytime
# Default: false
#
#sblim.wbem.cimxmlParser.allowEmptyLocalNameSpacePath=false

[Dave Blaschke]

The community review is completed and we received no substantial criticism. Therefore the patch has been approved and merged into the "HEAD" branch. The next release will pick it up.

[Dave Blaschke]

The patch was picked up by release 2.2.5 and will be closed.