[Sblim-issues] [ sblim-Bugs-3582039 ] SFCB should reject empty <VALUE> in most instances

[SourceForge.net <no...@so...>]

Bugs item #3582039, was opened at 2012-10-30 15:34
Message generated for change (Comment added) made by buccella
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712784&aid=3582039&group_id=128809

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: sfcb
Group: Standards Compliance
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Chris Buccella (buccella)
Assigned to: Chris Buccella (buccella)
Summary: SFCB should reject empty <VALUE> in most instances

Initial Comment:
According to DSP0201:

5.2.3.1 - VALUE
The VALUE element is used to define a single (non-array), non-reference, non-NULL CIM property value,
CIM qualifier value, CIM method return value, or CIM method parameter value.

Currently, SFCB allows for empty VALUE elements, giving them a CMPI_goodValue state. The spec allows for empty VALUE elements for the string type (the value becomes a zero-length string), but not for scalar types. The current implementation in SFCB, causes a problem, since both empty and 0 for a scalar type are the same.

The CIMType or ParamType attribute of the parent (or grandparent) tag can be checked for the type of VALUE.

----------------------------------------------------------------------

Comment By: Chris Buccella (buccella)
Date: 2012-12-13 14:54

Message:
pushed to git master

----------------------------------------------------------------------

Comment By: Chris Buccella (buccella)
Date: 2012-12-12 16:02

Message:
committed to HEAD

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=712784&aid=3582039&group_id=128809