Recent changes to bugs

Corrupt HTTP header

Patrik — Tue, 01 Apr 2008 09:28:52 -0000

Using other default Locales than English might corrupt the Date HTTP header when communicating with the CIM Server.

The problems occurs in the format "EEE, dd MMM yyyy HH:mm:ss 'GMT'" on row 53 in Header.Java in the package: javax.wbem.client.adapter.http.transport

For example, Monday in Swedish gets shortened to "Mån" which contains characters not accepted. The same problem might occur with the Month abbreviation.

Proposed solution:
Change the row 53 in Header.java to:

dateFormat = new SimpleDateFormat("EEE, dd MMM yyyy HH:mm:ss 'GMT'", Locale.ENGLISH);

And the addition of "import java.util.Locale;" of course.

-Patrik

Fixed bug in createInstance() by returning created one

Zhang Jun Wei — Thu, 18 May 2006 08:49:28 -0000

Modified class CIMOMImpl.java:

public CIMObjectPath createInstance(CIMObjectPath op,
CIMInstance ci) throws CIMException
{
if (op.getNameSpace().equalsIgnoreCase(SYSTEMNS) &&
ci.getClassName().equalsIgnoreCase
("Solaris_CIMOM"))
{
throw new CIMException
(CIMException.CIM_ERR_NOT_SUPPORTED);
}
aclCheck(ci);
ps.addCIMElement(op.getNameSpace(), ci);

//fix bug by zjw-begin
op.setKeys(ci.getKeys());
//fix bug by zjw-end

return op;
}

Fixed bugs in passing RefArray parameters

Zhang Jun Wei — Thu, 18 May 2006 08:29:23 -0000

XMLParser
1.CIMParameter getCIMParameter(Node node)
{
...
if (nodename.endsWith(".REFARRAY")) {
int refSize = cp.getSize();
if ( refSize <= 0) {
refSize = CIMDataType.SIZE_UNLIMITED;
}
cp.setType(new CIMDataType(refclassname,
refSize));//fix bug by zjw
}
...
}

2.CIMValue getCIMValue(Node node, String type)
{
...
} else if (nodename.equals(CIMXml.VALUE_ARRAY))
{
Vector v = new Vector();
for (node = walker.getNextElement(CIMXml.VALUE);
node != null; ) {
v.addElement(valueObject(node, type));
node = walker.getNextElement(CIMXml.VALUE);
}
o = v;
break;
}
//fix bug by zjw: begin
else if(nodename.equal(CIMXml.VALUE_REFARRAY))
{
Vector v = new Vector();
for (node = walker.getNextElement
(CIMXml.VALUE_REFERENCE); node != null; ) {
v.addElement(getCIMObjectPath
(getFirstChildElement(node)));
node = walker.getNextElement
(CIMXml.VALUE_REFERENCE);
}
o = v;
break;
}
//fix bug by zjw: end
...
}

Reference arrays not handled for method 'out' arguments

andy abendschein — Wed, 19 Oct 2005 05:01:56 -0000

It appears that methods that have 'out' arguments of
type 'reference array' are not being handled by the
response message parser.

According to version 2.2 of the DMTF DTD for XML
messages, the PARAMVALUE element may have one of the
following child elements: VALUE, VALUE.REFERENCE,
VALUE.ARRAY, or VALUE.REFARRAY.

I suspect that the problem lies in the getCIMValue()
method of the XMLParser class. A code inspection
reveals that child elements VALUE, VALUE.REFERENCE, and
VALUE.ARRAY are being handled, but VALUE.REFARRAY is not.

Here is the relevent section of the DTD:

<!ELEMENT PARAMVALUE (VALUE | VALUE.REFERENCE |
VALUE.ARRAY | VALUE.REFARRAY)?>
<!ATTLIST PARAMVALUE
%CIMName;
%ParamType; #IMPLIED
>

Thanks for checking it ou,

Andy

mofcomp file-separator problem with CIM 2.10

Paris Bingham — Wed, 07 Sep 2005 22:35:38 -0000

Found this while trying to utilize the new CIM 2.10
schemas with
wbemservices...

With CIM 2.10, the MOF files have been organized better by
"function" into subdirectories. There is a new file,
cimv210.mof,
at the top level that includes all of the underlying
MOF files, much
like CIM_Schema.mof did for earlier versions of CIM.
In this
file, the includes are structured like so:

#pragma include ("System\CIM_DiagnosticResult.mof")

On Win, there's no problem. However, on nixen, the MOF
compiler
complains about file-not-found. Changing the backslash to
forward-slash fixes the problem of nix'es, but then Win
is unhappy.
With previous versions of CIM_Schema.mof, there were no
partial directory specs to worry about, but there are
now with 2.10.

mofcomp file-separator problem with CIM 2.10

Paris Bingham — Wed, 07 Sep 2005 22:16:04 -0000

Found this while trying to utilize the new CIM 2.10
schemas with
wbemservices...

#pragma include ("System\CIM_DiagnosticResult.mof")

CIM-XML: No ARRAYSIZE attribute for bounded arrays

Paris Bingham — Wed, 07 Sep 2005 22:08:19 -0000

With both the 1.0.2 and current CVS MOF compilers, when
generating
the CIM-XML files from MOFs, the ARRAYSIZE attribute is
missing from
property declarations that are arrays. For example, in
MOF, the
CIM_Memory class has an array property, ErrorData:

uint8 ErrorData[64];

but in the generated CIM-XML, there is no ARRAYSIZE
attribute
showing the bounds of the array for ErrorData

<PROPERTY.ARRAY CLASSORIGIN="CIM_Memory"
NAME="ErrorData" TYPE="uint8">

CIMDateTime does not take account of DayLight Savings time

Anonymous — Thu, 14 Jul 2005 20:00:52 -0000

When in daylight savings time, passing a Date or Calendar
Object to the constructor of CIMDateTime does not give a
correct time offset to GMT.

For exaple, when in PST Daylight time (9 hours behind
GMT) you the conversion thinks you are 8 hours behind.

The problem lies in the getCalendarString method. It is
because this method get the TZ offset, but not the Daylight
time offset, hence the hours difference.

Reference class not getting populated in CIMParameter

Troy — Wed, 23 Mar 2005 17:48:47 -0000

When creating a CIMParameter object that contains a
REFARRAY, the class of the parameter fails to be
populated.

This can be fixed easily in the
javax.wbem.cimxml.XMLParser file. All that needs to
be done is in the getCIMParameter method, pass the
refclassname to the creation of the CIMDataType if the
nodename.endsWith(".REFARRAY").

SetInstance object path vs instance

Anonymous — Tue, 01 Mar 2005 18:42:05 -0000

eric.arnett@engenio.com

The SetInstance method passes providers an object
path derived from the instance that is to be set, instead
of passing on the object path provided by the client. In
the case where the properties to be modified are key
properties, this resulting object path changes, and the
instance to be modified cannot be found by the provider,
resulting in a CIM_ERROR_NOT_FOUND.