Re: Passing in Additional parameters in DataProvider Adapter not supported ?

Sorry for the confusion, I wanted to pass in the HostSystem - contextObject information to the DAP  for my custom object , for which I have posed this question . My plugin in is an extended point of vsphere.core.host.manage.storageViews.

The DAP which needs to get network information for a a specific host. Without using the relationship constraint I want to pass in the HostSystem(_contextObject or it _contextObject.uid )  as one of the parameters in the request .

To verify/experiment if the above functionality works I built a  modified example similar to the Chassis-ui example and with the following additions.

So my question still remains is the addPropertyParameter in DataByModelRequest class work ? Is this the right way to pass down additional parameters ?

Here is a modified version of the Chassis-ui Example :with the emphasis on testDBMR.addPropertyParameter("ContextUID",ctxObject);

var requestInfo:DataRequestInfo = new DataRequestInfo(DataUpdateSpec.newImplicitInstance());

var testDBMR:DataByModelRequest = DataByModelRequest.newInstance(_contextObject,ChassisSummaryDetails,requestInfo);

var ctxObj:Object=Object(_contextObject);

testDBMR.addPropertyParameter("ContextUID",ctxObj);

      // Dispatch an event to fetch _contextObject data from the server

      // along the specified model.

      dispatchEvent(testDBMR);

However the response doesn't show up the Parameter Spec :

Modified version of code in service layer

Service Layer:

But the ParameterSpec in the QueryRequest show up as zero and the property itself is null .

2012-12-20 13:52:11.548] INFO  [INFO ] http-bio-9443-exec-8          System.out                                                      

[2012-12-20 13:52:11.548] DEBUG [DEBUG] http-bio-9443-exec-8          com.vmware.vise.data.query.impl.DataServiceImpl                   QuerySpecs to execute:

Query[0]:

QuerySpec

   QueryName: dam-auto-generated: ListViewMediator:dr-39

   ResourceSpec

      Constraint: Constraint

         TargetType: samples:Chassis

      PropertySpec[1]

         ProviderType: samples:Chassis

         Relationship: null

         Properties[2]

            PropertyName: name

            PropertyName: serverType

   ResultSpec:

      Offset: 0

      MaxResultCount: 70

      OrderingCriteria: null

[2012-12-20 13:52:11.549] INFO  [INFO ] http-bio-9443-exec-8          System.out                                                        DEBUG-pSpec0

[2012-12-20 13:52:11.549] DEBUG [DEBUG] data-service-pool-173         com.vmware.vise.util.session.SessionUtil                          Client id is - c80c761d-4c4b-46b5-a711-f9fcd3cb6222, associated with http session id 9F09C4A58CE6CCF0CB4E1C8C38F550EE with context path /vsphere-client-endpoints

[2012-12-20 13:52:11.549] DEBUG [DEBUG] data-service-pool-173         com.vmware.vise.util.session.SessionUtil                          Client id is - c80c761d-4c4b-46b5-a711-f9fcd3cb6222, associated with http session id 9F09C4A58CE6CCF0CB4E1C8C38F550EE with context path /vsphere-client-endpoints

[2012-12-20 13:52:11.549] INFO  [INFO ] http-bio-9443-exec-8          System.out                                                        DEBUG params length is zero

[2012-12-20 13:52:11.549] DEBUG [DEBUG] data-service-pool-173         com.vmware.vise.util.session.SessionUtil                          Client id is - c80c761d-4c4b-46b5-a711-f9fcd3cb6222, associated with http session id 9F09C4A58CE6CCF0CB4E1C8C38F550EE with context path /vsphere-client-endpoints

[2012-12-20 13:52:11.549] DEBUG [DEBUG] data-service-pool-173         com.vmware.vise.util.session.SessionUtil                          Client id is - c80c761d-4c4b-46b5-a711-f9fcd3cb6222, associated with http session id 9F09C4A58CE6CCF0CB4E1C8C38F550EE with context path /vsphere-client-endpoints

[2012-