version 1.64, 2002/02/19 18:07:15
|
version 1.87, 2002/03/21 23:19:53
|
|
|
| |
2. (Markus Mueller) 05 Feb 2002 - AIX support. | 2. (Markus Mueller) 05 Feb 2002 - AIX support. |
| |
3. KS - 18 Feb 02 Add changes to test for and set the NULL value for CIMValues. |
3. (Sushma Fernandes - HP) 13 Feb 2002 Implemented FileSystemPropertyOwner |
|
class to support PEGASUS_HOME dependent properties like Repository |
|
location, Provider location and Consumer location. |
|
The default location for these properties continue to be the same |
|
as before. Added support to the Config Manager to own the |
|
Pegasus Home variable and implemented method (getHomedPath) to |
|
return absolute paths based from Pegasus Home. |
|
|
|
For more information look in to the following files: |
|
pegasus/src/Pegasus/Config/ConfigManager.h |
|
pegasus/src/Pegasus/Config/ConfigManager.cpp |
|
pegasus/src/Pegasus/Config/FileSystemPropertyOwner.h |
|
pegasus/src/Pegasus/Config/FileSystemPropertyOwner.cpp |
|
|
|
4. KS - 18 Feb 02 Add changes to test for and set the NULL value for CIMValues. |
This forces new CIMValues to have a NULL attributes that is only | This forces new CIMValues to have a NULL attributes that is only |
reset when a value is "set" or copied into them. the XML and MOF | reset when a value is "set" or copied into them. the XML and MOF |
also deliver a NULL value back when the state of the CIMValue is NULL. | also deliver a NULL value back when the state of the CIMValue is NULL. |
There is a remaining addition to put an exception on CIMValue gets when | There is a remaining addition to put an exception on CIMValue gets when |
the NULL attribute is set that we will install later. | the NULL attribute is set that we will install later. |
| |
4. KS - 19 Feb 2002 Extended testclient slightly and cleaned up numerous bugs. |
5. KS - 19 Feb 2002 Extended testclient slightly and cleaned up numerous bugs. |
| |
5. KS - 19 Feb 2002 - Add workpaper in doc/workpaper defining the Pegasus Qualifiers. |
6. KS - 19 Feb 2002 - Add workpaper in doc/workpaper defining the Pegasus Qualifiers. |
Note that this version of the paper still needs work. | Note that this version of the paper still needs work. |
| |
|
7. (Nag Boranna - HP) 20 Feb 2002 - Modified HTTPAcceptor to optionally bind to |
|
loopback host. Modified CIMClient to connect to loopback host when connectLocal() |
|
method is used. Added a new method lookupPort() in System.h to return the system |
|
configured wbem port number. Modified cimuser, cimauth and cimconfig CLI's to use |
|
modified CIMClient connectLocal() interface. |
|
|
|
8. (KS- 21 Feb 2002) - Modified Makefile for repository load so located in |
|
schema directory. The one in src/pegasus/compiler/load is deprecated and |
|
will be deleted. |
|
|
|
9. KS-21 Feb 2002 - Added new constructor to CIMValue and associated tests |
|
|
|
10. RK-20 Feb 2002 - Add Array reference to CIMValue and added tests |
|
|
|
11. (Sushma Fernandes - HP, Nag Boranna - HP) 22 Feb 2002 Implemented |
|
checks for privileged user when performing authorization. |
|
Added a configuration property enableRemotePrivilegedUserAccess. |
|
This property needs to be set to true to enable privileged user access |
|
for remote clients. |
|
|
|
12. (Roger Kumpf - HP) 22 Feb 2002 - Added type information to extrinsic |
|
method (InvokeMethod) operations. This change involves the addition |
|
of PARAMTYPE attributes to PARAMVALUE and RETURNVALUE tags. This tag |
|
allows the server to determine the type of a parameter value without |
|
having to look up the method definition in the schema. It also allows |
|
the client API to do the same for output parameters as well as return |
|
values. |
|
|
|
PROVIDER IMPLICATIONS: |
|
|
|
Method providers ARE affected by this change. Previously, all input |
|
parameters to invokeMethod were sent to the provider as String type |
|
regardless of what the client actually specified or how the method |
|
was defined. With this change, providers will now receive input |
|
parameters of the type that was actually specified by the client |
|
application (regardless of how the method was defined in the schema). |
|
|
|
However, parameters coming from clients other than the Pegasus client |
|
API may omit the PARAMTYPE attribute. In this case, the operation |
|
processor (currently dispatcher) will find these "typeless" parameters |
|
and convert them to the correct type based on the method definition. |
|
The result is that if the client specifies the parameter type in the |
|
XML encoding (as the Pegasus client API does), the method provider |
|
will receive the type specified by the client; if the client does not |
|
specify the parameter type, the method provider will see the type |
|
specified in the method definition. |
|
|
|
CLIENT IMPLICATIONS: |
|
|
|
Clients ARE affected by this change. Any output parameters that are |
|
returned from Pegasus (or other CIM servers using the PARAMTYPE |
|
attribute) will now be received by Pegasus clients as the same type |
|
sent by the server. Previously, they would have always been of |
|
String type. In addition, the return value will be received as the |
|
correct type rather than as a String. |
|
|
|
Parameters coming from servers other than Pegasus may omit the |
|
PARAMTYPE attribute. In this case, the client will see a |
|
CIMParamValue with type==CIMType::NONE, with a CIMValue of type |
|
String. Similarly, return values coming from other servers that omit |
|
PARAMTYPE will be seen by the client as String type. These return |
|
values will NOT have the CIMType::NONE hint that parameters get, |
|
because they are CIMValues rather than CIMParamValues. |
|
|
|
This behavior will remain for the forseeable future (through |
|
Pegasus version 2), as it is not possible to require that other |
|
implementations use the PARAMTYPE attribute. |
|
|
|
SIDE EFFECTS: |
|
|
|
In the process of implementing this functionality, I discovered |
|
that there was no way to set a CIMValue to be an array of |
|
CIMReferences. This appeared to be an oversight, since method |
|
parameters are permitted to be arrays of CIMReferences. I've |
|
added the necessary functionality to the CIMValue class. |
|
|
|
I also found that the CIMParamValue class needed significant |
|
clean-up, which I completed. |
|
|
|
SETPROPERTY CHANGES: |
|
|
|
A similar problem in SetProperty operations was addressed by |
|
"typing" the specified property value in the operation processor |
|
(currently dispatcher). This is achieved by looking up the |
|
relevant schema to get the property definition, and then converting |
|
the specified value to that property's type. |
|
|
|
The SetProperty operation encoding has not changed to accomodate |
|
inclusion of type information that would obviate the need for this |
|
extra processing. However, clients can avoid this overhead by using |
|
ModifyInstance operations (with a property list) instead of SetProperty. |
|
|
|
The GetProperty operation also has NOT been updated with type |
|
information. Client applications using the Pegasus client API will |
|
always receive String or reference values when calling GetProperty |
|
against any server (Pegasus or not). Clients that require properties |
|
to be returned as the correct type must use GetInstance (perhaps with |
|
a property list) rather than GetProperty. |
|
|
|
13. (Roger Kumpf - HP) 22 Feb 2002 - Reworked the CIMParamValue class. |
|
Instead of being composed of a CIMParameter and a CIMValue, this |
|
class is now composed of a String (parameter name) and a CIMValue. |
|
This change removes the redundancy of having the type, isArray, |
|
and arraySize members in both the CIMParameter and the CIMValue. |
|
The new CIMParamValue definition is more consistent with the XML |
|
encoding of parameter values. |
|
|
|
An isTyped member was also added to CIMParamValue to support the |
|
behavior outlined in item 12 above. Clients should use the isTyped() |
|
method to determine whether the output parameters returned from |
|
InvokeMethod operations are of the correct type, or whether they |
|
have defaulted to String type. |
|
|
|
14. (KS) 4 March 2002 - Corrections for NULL value and the XML code. |
|
Corrections to compiler for Null values input (parser and valuectory) |
|
|
|
15. (Nag Boranna - HP) 04 March 2002 - Modified CIMClient API to accept |
|
username and password as parameters to connect() method, added a new |
|
method diconnect() that closes the open connection with the server |
|
and added code to handle HTTP Basic authentication challenges from |
|
the server. |
|
|
|
16 (KS) 4 March 2002 - Correct problem with array constants not picking up |
|
all of the entires in the array. Bugzilla bug # 6. |
|
|
|
17. (Yi Zhou - HP) 4 March 2002 - Implemented provider registration manager |
|
to perform efficient lookup of instance provider, method provider, and |
|
indication provider. Also, implemented provider registration instances |
|
operations. |
|
|
|
Modified registration provider to use latest provider registration schema. |
|
|
|
18 (KS) 6 March 2002 - Implemented changes to compiler and flavors to correct the |
|
definition of CIMFlavors. |
|
|
|
|
|
19. (Roger Kumpf - HP) 1 Mar 2002 - Reworked the XmlWriter class to |
|
eliminate many of the redundant memory copies that resulted from the |
|
nested method call structure. Now, instead of having a method at |
|
each level that adds a begin tag, contents, and an end tag, there |
|
are separate methods to add the begin and end tags. At the top |
|
level, each of the begin tag methods are called, then the message |
|
"body" is added, followed by calls to the end tag methods. |
|
|
|
The message body is currently still copied twice, once into the XML |
|
payload and then again when the HTTP header is added. (Since the |
|
HTTP header contains a content length field, the header cannot be |
|
constructed until the payload is complete.) It is possible to |
|
remove these extra copies as well, but that would require additional |
|
changes elsewhere in the code. For example, the HTTPMessage class |
|
would need to hold the headers and payload separately rather than in |
|
a single buffer. |
|
|
|
Along with these changes, I did a lot of cleanup. Much of the XML |
|
formatting code has been moved from CIMReference to XmlWriter. Also, |
|
error message formatting has been consolidated in XmlWriter from the |
|
various encoders and decoders, etc. |
|
|
|
20. (Roger Kumpf - HP) 5 Mar 2002 - Added checks in the |
|
CIMOperationRequestDecoder and CIMExportRequestDecoder to validate |
|
that the information in the HTTP headers of a request is consistent |
|
with what is encoded in the XML request itself. |
|
|
|
Specifically, the CIMOperation, CIMProtocolVersion, CIMMethod, |
|
CIMObject, CIMBatch, CIMExport, and CIMExportBatch headers are |
|
validated. |
|
|
|
21. (KS) 7 March 2002 - Correct error in qualifier propagation processing in |
|
qualifierlist.resolve. Temporarily remove the DEFAULT setup on the |
|
Compiler qualifier generation. Add tests for resolve processing. |
|
|
|
22. (Roger Kumpf - HP) 8 Mar 2002 - Simplified CIMClient API construction. |
|
Previously, the client application constructed a client API using: |
|
|
|
Monitor* monitor = new Monitor; |
|
HTTPConnector* connector; |
|
connector = new HTTPConnector(monitor); |
|
Uint32 timeoutMillis = 60 * 1000; // optional |
|
|
|
CIMClient client(monitor, connector, timeoutMillis); |
|
|
|
With this change, the client application now looks like: |
|
|
|
Uint32 timeoutMillis = 60 * 1000; // optional |
|
|
|
CIMClient client(timeoutMillis); |
|
|
|
The old style allowed an SSL context to be specified in the HTTPConnector |
|
constructor. It seems that the SSL context is really a property of a |
|
connection rather than of the client API. So instead of adding an SSL |
|
context parameter to the CIMClient constructor, I added it to the CIMClient |
|
connect() method. There are now forms of the connect() method with and |
|
without an SSL context. Similar changes were made in the HTTPConnector |
|
class to allow specification of an SSL context in the connect() method |
|
rather than in the constructor. |
|
|
|
NOTE: Client applications are affected and must be updated with this |
|
change. I've already updated all the clients that are checked in and |
|
included in the Pegasus build. |
|
|
|
23. (KS) 8 March 2002 - Correct error in compiler that caused length field |
|
of fixed length arrays to be lost. |
|
|
|
24. (Jenny Yu - HP) 8 March 2002 - Modified the CIMException class to NOT |
|
include the source filename and line number in the exception message. |
|
However, for anyone who wishes to include such information in the |
|
CIM Exception message, a compile option DEBUG_CIMEXCEPTION can be used |
|
for that purpose. |
|
|
|
A couple of changes have been made to the Tracer class: |
|
|
|
- CIMException messages can now be put in a trace file using the Tracer. |
|
A new interface has been added to the Tracer to accept a CIMException |
|
as input and writes the exception message in the CIMException to the |
|
trace file. This message will include the source filename and the |
|
line number of the CIMException originator. |
|
|
|
Tracer::traceCIMException(traceComponent, traceLevel, cimException); |
|
|
|
- Strings can now be traced using the Tracer class: |
|
A new interface has been added to the Tracer to accept a String as |
|
input and writes the String to the trace file. |
|
|
|
(ex.) |
|
You can issue the following method call: |
|
Tracer::trace(TRC_CONFIG, Tracer::LEVEL2, "Operation Failed."); |
|
|
|
or use the following new macro: |
|
PEG_TRACE_STRING(TRC_CONFIG, Tracer::LEVEL2, "Operation Failed."); |
|
|
|
25. (Ramnath Ravindran - Compaq) 11 March 2002 - added IPCTru64.h and modified |
|
several files so that Pegasus could build and run on Tru64 unix. Added |
|
one macro in ConfigUnix and ConfigWindows (PEGASUS_OR_IOS_BINARY) in |
|
the case where std::ios::binary is present with a bitwise OR operator. |
|
This macro only works when the std::ios::binary is NOT the first |
|
operator to be "OR"ed. |
|
|
|
26. (Ramnath Ravindran - Compaq) 12 March 2002 - modified more files so that |
|
Pegasus could build and run on Tru64 unix. Finished replacing instances |
|
of ios::binary with the macros PEGASUS_IOS_BINARY and |
|
PEGASUS_OR_IOS_BINARY. Also modified some code that dealt with file |
|
streams. Tru64 does not support the use of the " != " operator on a |
|
fstream object. Instances of such were either modified or an ifdef |
|
block detecting a build on Tru64 was used. Added cstdarg and ctime in |
|
pegasus/src/stdcxx/cwrappers/ directory. |
|
|
|
27. (Mary Hinton) 16 March 2002 - fixed the CIMServer so that it could once |
|
again be installed as a Windows service. The repositoryRootPath could |
|
not be found, because the pegasusHome variable was not being set properly |
|
in the Windows service work thread. |
|
|
|
28. (Bob Blair by KS) 17 March 2002 - Modified repository so there is both a |
|
local repository (cimmofl) and a client interface repository (cimmof) |
|
executable |
|
|
|
29. (KS ) 18 March 2002 - Modified schema makefiles to use the cimomfl respository |
|
executable. |
|
|
|
30. (Roger Kumpf - HP) 19 Mar 2002 - Added range checking for Uint* and |
|
Sint* values in XmlReader.cpp. Previously, values that were out of |
|
range were simply truncated to fit the given integer size. An |
|
exception is now thrown when the given string can not be parsed into |
|
an integer of the specified size. |
|
|
|
31. (Roger Kumpf - HP) 20 Mar 2002 - Added support for hexadecimal integers |
|
in XmlReader.cpp. |
|
|
|
32. (Nag Boranna - HP) 21 March 2002 - Implemented server side Basic |
|
Authentication handling code and cleaned up ATTN's in the authentication |
|
releated files. Implemented a new AuthenticationInfoRep class and modified |
|
the related files. Added more test cases to test the authentication classes. |
|
|
|
33. (Ramnath Ravindran - Compaq) 21 March 2002 - replaced instances of "| ios::binary" with PEGASUS_OR_IOS_BINARY in 3 files: System.cpp, InstanceIndexFile.cpp, and |
|
InstanceDataFile.cpp |
------------------------------------------------------------------- | ------------------------------------------------------------------- |
Version 1.06 working towards 1.1 Started 13 December 2001 | Version 1.06 working towards 1.1 Started 13 December 2001 |
| |
|
|
| |
60. (Bapu Patil - HP) Updated makefiles to support HP-UX IA64 bits O.S. | 60. (Bapu Patil - HP) Updated makefiles to support HP-UX IA64 bits O.S. |
| |
61. (Sushma Fernandes - HP) 13 Feb 2001 Implemented FileSystemPropertyOwner |
|
class to support PEGASUS_HOME dependent properties like Repository |
|
location, Provider location and Consumer location. |
|
The default location for these properties continue to be the same |
|
as before. Added support to the Config Manager to own the |
|
Pegasus Home variable and implemented method (getHomedPath) to |
|
return absolute paths based from Pegasus Home. |
|
|
|
For more information look in to the following files: |
|
pegasus/src/Pegasus/Config/ConfigManager.h |
|
pegasus/src/Pegasus/Config/ConfigManager.cpp |
|
pegasus/src/Pegasus/Config/FileSystemPropertyOwner.h |
|
pegasus/src/Pegasus/Config/FileSystemPropertyOwner.cpp |
|
|
|
--------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
Version 1.1 - July 2001 Development branch | Version 1.1 - July 2001 Development branch |
Tagged as version_1_01 on 3 August 2001 (sorry should have been | Tagged as version_1_01 on 3 August 2001 (sorry should have been |