Re: embedded CIM Instance
Kirk Augustin <[email protected]>
| Newsgroups | gmane.network.open-pegasus.general |
|---|---|
| Message-ID | <[email protected]> |
There is not much difference between an array of key strings that you can use to get the instances, and the instances themselves. I don't use CMPI very much, but normally in CIM, the key strings is all you would expect. Kirk Augustin 11821 NW McNamee Rd Portland, OR 97231 ________________________________ From: "[email protected]" <[email protected]> To: [email protected] Sent: Thursday, August 18, 2011 9:53 PM Subject: embedded CIM Instance Hi all, We need to return an array of CIM Instances in a vendor extension method in our CMPI Provider. we have defined the method as follows: uint32 xxx( [IN (false), OUT, Description ("xxx"), EmbeddedInstance( "Our_Class")] string instances[]); From provider code we are adding out argument of type CMPI_instanceA. Our client uses SBLIM 2.0.9.3 to get CIM Instances. When we are using OpenPegasus as a CIMOM, client receives the data as an array of CIM Instances properly. But when we use SFCB in Vmware ESX as CIMOM . Client is receiving it as array of strings only, not as CIM Instances. Any help? Thanks and regards, Souvik Roy Wipro Technologies Block - DM, Sector -V Salt Lake. Kolkata- 700091. India VOIP: 8584750 Direct: +91 33 30954750 Only when the last tree has died and the last river been poisoned and the last fish been caught will we realise we cannot eat money Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com