Standards Based Linux Instrumentation / Bugs / #2558 SFCB should reject empty <VALUE> in most instances

#2558 SFCB should reject empty <VALUE> in most instances

Milestone: Standards_Compliance

Status: pending-fixed

Owner: Chris Buccella

Labels: sfcb (1090)

Component:

Priority: 5

Updated: 2012-12-13

Created: 2012-10-30

Creator: Chris Buccella

Private: No

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.

Discussion

Chris Buccella - 2012-12-12

patch for 1.3

3582039-reject_empty_VALUE.patch

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Chris Buccella - 2012-12-13

committed to HEAD

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Chris Buccella - 2012-12-13

status: open --> pending-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Chris Buccella - 2012-12-13

pushed to git master

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

SFCB should reject empty <VALUE> in most instances

Group

Searches

Help

#2558 SFCB should reject empty <VALUE> in most instances

Discussion