Menu

#2537 CR03: Add new data types for PARAMVALUE

closed-fixed
jsr48-client
4
2013-12-13
2012-09-18
No

The Java CIM Client does not appear to implement DMTF CRCIMXML00003:

Background/Rationale:

The extrinsic PARAMVALUE element was added to IMETHODRESPONSE to support new intrinsic operations in DSP0200. This should have been the intrinsic IPARAMVALUE. We were going to leave this alone, as we had thought there where no output parameters that needed the extended capabilities provided by the IPARAMVALUE element. However, we found that was untrue, as the PullQueryInstances operation has an output parameter that returns a CLASS element. Unfortunately, there are several implementations in the field already utilizing PARAMVALUE. So rather than simply utilizing IPARAMVALUE, we are instead proposing to extend PARAMVALUE to handle the additional datatypes handled by IPARAMVALUE.

Requested Change:
Replace line 802 of DSP0201 as indicated to add missing types found in IPARAMVALUE:
<!ELEMENT PARAMVALUE (VALUE|VALUE.REFERENCE|VALUE.ARRAY|VALUE.REFARRAY)?>

<!ELEMENT PARAMVALUE (VALUE|VALUE.ARRAY|VALUE.REFERENCE|VALUE.REFARRAY|CLASSNAME|INSTANCENAME|QUALIFIER.DECLARATION|
CLASS|INSTANCE|VALUE.NAMEDINSTANCE)?>

Change line 850 of DSP0201 as indicated to match number of parenthesis in DSP0203::

<!ELEMENT IMETHODRESPONSE (ERROR| (IRETURNVALUE?, PARAMVALUE*))>

Change line 276 of DSP0203 as indicated:

<!ELEMENT PARAMVALUE (VALUE|VALUE.REFERENCE|VALUE.ARRAY|VALUE.REFARRAY)?>

<!ELEMENT PARAMVALUE (VALUE|VALUE.ARRAY|VALUE.REFERENCE|VALUE.REFARRAY|CLASSNAME|INSTANCENAME|QUALIFIER.DECLARATION|
CLASS|INSTANCE|VALUE.NAMEDINSTANCE)?>

1 Attachments

Discussion

  • Dave Blaschke

    Dave Blaschke - 2012-09-18
    • summary: DMTF CRCIMXML00003 --> Implement DMTF CRCIMXML00003
     
  • Dave Blaschke

    Dave Blaschke - 2013-01-14
    • priority: 5 --> 4
     
  • Dave Blaschke

    Dave Blaschke - 2013-01-14

    Lowering priority one notch below normal, this bug is dependent on DMTF CIM-XML changes

     
  • Dave Blaschke

    Dave Blaschke - 2013-01-15
    • summary: Implement DMTF CRCIMXML00003 --> Add new data types for PARAMVALUE
     
  • Dave Blaschke

    Dave Blaschke - 2013-01-24
    • summary: Add new data types for PARAMVALUE --> CR03: Add new data types for PARAMVALUE
     
  • Dave Blaschke

    Dave Blaschke - 2013-02-20

    Classic ID #3569106

     
  • Dave Blaschke

    Dave Blaschke - 2013-02-20
    • component: --> jsr48-client
     
  • Dave Blaschke

    Dave Blaschke - 2013-04-30

    DSP0201 2.4.0a-rc1 was published yesterday. It contains the following:

    1607 5.3.6.5 PARAMVALUE
    
    1608 The PARAMVALUE element defines the value of an input or output parameter of an extrinsic method call,
    1609 or the value of an output parameter of an intrinsic method call. Note that input parameters of intrinsic
    1610 method calls are represented by the IPARAMVALUE element; this inconsistency for intrinsic methods has
    1611 historical reasons.
    
    1612   <!ELEMENT PARAMVALUE (
    1613      VALUE | VALUE.REFERENCE | VALUE.ARRAY | VALUE.REFARRAY |
    1614      CLASSNAME | INSTANCENAME | CLASS | INSTANCE | VALUE.NAMEDINSTANCE)?>
    1615   <!ATTLIST PARAMVALUE
    1616      %CIMName;
    1617      %ParamType; #IMPLIED
    1618      %EmbeddedObject;>
    
     
  • Dave Blaschke

    Dave Blaschke - 2013-10-17
    • status: open --> open-fixed
     
  • Dave Blaschke

    Dave Blaschke - 2013-10-17

    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

    Dave Blaschke - 2013-11-06
    • status: open-fixed --> pending-fixed
     
  • Dave Blaschke

    Dave Blaschke - 2013-11-06

    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

    Dave Blaschke - 2013-12-13
    • status: pending-fixed --> closed-fixed
     
  • Dave Blaschke

    Dave Blaschke - 2013-12-13

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

     

Log in to post a comment.