I don't see any use case where it's not possible to have a service reference - and tools could just query the mbeans as an alternative
Carsten 2013/8/14 Felix Meschberger <[email protected]> > Hi > > Am 14.08.2013 um 11:37 schrieb Bertrand Delacretaz: > > > On Wed, Aug 14, 2013 at 11:33 AM, Carsten Ziegeler <[email protected]> > wrote: > >> ...I mean not having these at all :) and just have them as service > >> properties. Filtering services based on the tags can be done using the > >> filter expression based on service properties and registering the > checks as > >> mbeans works this way as well... > > > > Ok, that's how it's done now. > > > >> Do we have other use cases ? > > > > We need some of these values (HC name and tags at least) in the > > webconsole and MBeans when we output a Result. We usually don't have a > > ServiceReference there, just HealthCheck, so it's much more convenient > > to be able to access that info from a HealthCheck. > > Yet: for the MBean the Health Check controller getting the HealthCheck > services and registering MBeans on behalf of them could as well leverage > the ServiceReference properties to setup the MBean's objectname properties > or Attributes. I would assume the actual MBean registered will be a > proxy/wrapper to the HealthCheck service implementing the appropriate MBean > interface and embedding the ServiceReference and HealthCheck objects, or so. > > As for the Web Console: This is one of the reporting tools, I had in mind. > If the WebConsole directly accesses the services through the Service > Registry, it will also have the ServiceReference in hand ... > > But still, there may be report tooling not able to cope with > ServiceReferences ? > > Regards > Felix -- Carsten Ziegeler [email protected]
