Dan, Thanks for your reply. I did as you said and it works great.
I have another question: What exactly is the mechanism that Muse uses to determine the Capabilities a Manageable Resource defines? It appears to me that a Capability is created corresponding to each Namespace for which Resource Properties are declared. Each Capability URI appears to match the Namespace URI of the Resource Properties that are associated with it. Is this correct? Thanks Jared Zebedee -----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: Monday, August 27, 2007 10:34 AM To: [email protected] Subject: Re: Adding Custom Capabilities to ManageabilityCapability Resource Property For those capabilities that are management-oriented, change your capability's base class from AbstractWsResourceCapability to AbstractManageabilityCapability. The initialization code in the latter will add your capability's URI to the ManageabilityCapability property automatically. Dan "Jared A. Zebedee" <[EMAIL PROTECTED]> wrote on 08/26/2007 09:30:30 PM: > Greetings all, > > > > I have created a WSDM Manageable Resource with my own custom Manageability > Capabilities. The custom Capabilities are associated with my own custom > Resource Properties using declarations in the Resource Metadata Descriptor. > Everything compiles and runs fine, but when I retrieve the > 'ManageabilityCapability' Resource Property, I only see the standard WSDM > Capabilities (Identity, ManageabilityCharacteristics, and > OperationalStatus). > > > > Does anyone know how to add custom Capabilities to the > ManageabilityCapability Property? The custom Capabilities should be > included in the Property as soon as the Manageable Resource has started up. > > > > Thanks > > > Jared Zebedee > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
