version 1.57, 2002/01/24 19:10:33
|
version 1.71, 2002/03/04 19:56:08
|
|
|
CHANGE LOG FOR PEGASUS | CHANGE LOG FOR PEGASUS |
|
|
|
|
|
Version 1.07 working towards 1.1 - Started 4 Feb 2002 |
|
Started just before cutover to the new dispatcher, etc. |
|
TAG: VERSION_1_07 |
|
|
|
1. KS - Updated pegsusversion to 1.07 and tagged file. |
|
|
|
2. (Markus Mueller) 05 Feb 2002 - AIX support. |
|
|
|
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 |
|
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. |
|
There is a remaining addition to put an exception on CIMValue gets when |
|
the NULL attribute is set that we will install later. |
|
|
|
5. KS - 19 Feb 2002 Extended testclient slightly and cleaned up numerous bugs. |
|
|
|
6. KS - 19 Feb 2002 - Add workpaper in doc/workpaper defining the Pegasus Qualifiers. |
|
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. |
|
|
|
------------------------------------------------------------------- |
Version 1.06 working towards 1.1 Started 13 December 2001 | Version 1.06 working towards 1.1 Started 13 December 2001 |
| |
1. Merged back to Main branch. All general development will be in main branch | 1. Merged back to Main branch. All general development will be in main branch |
|
|
service were both running. The service wasn't accessible to the TestClient | service were both running. The service wasn't accessible to the TestClient |
program. | program. |
| |
|
6. (Nitin Upasani - Jan 25, 2002) Operations on CIM_IndicationSubscription, |
|
CIM_IndicationHandlerCIMXML and CIM_IndicationFilter classes will be now processed |
|
in new queue, IndicationService which will get invoked from dispatcher. |
|
CIM_CREATE_INSTANCE_REQUEST_MESSAGE |
|
CIM_MODIFY_INSTANCE_REQUEST_MESSAGE |
|
CIM_DELETE_INSTANCE_REQUEST_MESSAGE |
|
CIM_GET_INSTANCE_REQUEST_MESSAGE |
|
CIM_ENUMERATE_INSTANCES_REQUEST_MESSAGE |
|
CIM_ENUMERATE_INSTANCE_NAMES_REQUEST_MESSAGE |
|
|
|
This new service will also take care of processing the indications on receiving |
|
CIM_PROCESS_INDICATION_REQUEST_MESSAGE. This message should come from |
|
IndicationProvider or some other mechanism which is not yet clear. |
|
|
|
IndicationService will also receive following messages from PG_ProviderRegistration |
|
when a new IndicationProvider will get registered. |
|
CIM_NOTIFY_PROVIDER_REGISTRATION_REQUEST_MESSAGE |
|
CIM_NOTIFY_PROVIDER_TERMINATION_REQUEST_MESSAGE |
|
|
|
I had also defined new Indication Provider APIs, enableIndication, disableIndication |
|
and modifyIndication with more parameters passed and eventually planning to terminate |
|
old APIs (provideIndication, cancelIndication and updateIndication). Also there is a |
|
plan to implement one more call as startIndication and will be done soon. |
|
|
|
There are three new test programs in IndicationService directory, which will create |
|
Filter, Indication and Subscription instances using IndicationService. |
|
|
|
Also modified sample IndicationProvider code with the new APIs introduced. |
| |
------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| |