You can reuse a capability implementation class in your resource type as long as the capability's initialize() method is idempotent. I'm assuming you want to do this so that clients who read the capability URI values from the ManageabilityCapability property will see multiple descriptive capabilities, but the implementation is all in one class. Otherwise, if you think it's simplest to define everything in one capability, you can just do that. Splitting up properties/operations into multiple capabilities is something you want to do if the smaller capabilities will be more reusable across different resource types.
Dan Keith Rochford <[EMAIL PROTECTED]> wrote on 07/23/2007 09:25:46 AM: > Hi All, > I'm having trouble figuring out the best approach to this problem. I'm > still new to this so apologies if it doesn't make sense! > > Consider a resource such as a server, in addition to performance metrics > etc, it might have several services which we want to monitor and manage. > In order to keep things tidy I was thinking that the best way to do this > might be to define a ServiceManagement Capability (with properties such > as service name, status, and operations such as start/stop) and create > one of these for each of the managed services. Is it possible to do this > with MUSE? to have multiple capabilities of the same type in a single > management endpoint? It doesn't seem to make sense to define a specific > capability for each service. > > Is there a better (or more WSDM-friendly) approach to achieve this? > > Should I try to use a factory object to create each of these > ServiceManagement Capabilities from within the code, along with a > specific EPR? > > I feel I'm missing something here. > > Any advice is very much appreciated & thanks for all the hard work so far! > > Kind regards > Keith > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
