Numeric keys are encoded as doubles. Considering doubles are not allowed as keys this seems to be an error. For example if a unit32 key value encoded as 0.0 rather than 0.
protected static final CIMObjectPath Demo_MethodClass_INSTANCCE = new CIMObjectPath(
"root/demo:Demo_MethodClass.Id=0")
the actual call is
final CIMArgument<?>[] inValues = new CIMArgument[0];
final CIMArgument<?>[] outValues = new CIMArgument[20];
final Object value = client.invokeMethod(Demo_MethodClass_INSTANCCE,
"No_Args", inValues, outValues);
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Seems like you stumbled on a special case with Id=0 because Id=-1, Id=1, etc. all seem to work fine. Heck, even Id=00 works, as does Id=0x0, just not Id=0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The community review has completed and we received no substantial critisism. Therefore the patch has been approved and merged into the "HEAD" branch. The next release will pick it up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
http://dmtf.org/sites/default/files/standards/documents/DSP0203_2.3.1.dtd specifies that KEYVALUES are (string | boolean | numeric).
Could you please post the XML request/response that pointed this issue out
Oops, misread the "encoded" part... any chance you could post a Java snippet of how you're generating the request? or a toString() of the instance?
The cop is declared with
protected static final CIMObjectPath Demo_MethodClass_INSTANCCE = new CIMObjectPath(
"root/demo:Demo_MethodClass.Id=0")
the actual call is
final CIMArgument<?>[] inValues = new CIMArgument[0];
final CIMArgument<?>[] outValues = new CIMArgument[20];
final Object value = client.invokeMethod(Demo_MethodClass_INSTANCCE,
"No_Args", inValues, outValues);
Seems like you stumbled on a special case with Id=0 because Id=-1, Id=1, etc. all seem to work fine. Heck, even Id=00 works, as does Id=0x0, just not Id=0.
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.
Patch against HEAD
The community review has completed and we received no substantial critisism. Therefore the patch has been approved and merged into the "HEAD" branch. The next release will pick it up.
The patch was picked up by release 2.1.8 and will therefore be closed.