RE: [picocontainer-dev] @Jörg - merging JMX stuff together

Konstantin Priblouda wrote on Monday, September 03, 2007 2:09 PM:

> Hi Jörg ( ant of course others interested ),
> 
> I would like to rework JMX and merge it together.
> IMHO it should have following properties:
>  - actual exposition is done by visitor, so adapter
> does not need mbean server on creation (like JNDI
> stuff),
> and not in getComponentInstance()

And how will you add now new uncached components on on-the-fly? A visitor is still a one-time task. My JMX components are created based on individual threads and a visitor does not help here at all.

>  - adapter holds object name ( if not, visitor will
>  try to create one based on some base name +
> stringified component key )

That's what the ObjectNameFactory is used for. See, the names are exposed to the client's admins and you may have to match really strong requriements about how names for components have to be build.

>  - deregistering on disposal / stop (for this puprose
> adapter shall keep reference to server)
> 
> 
> My most concern with current implementation is
> difficult configuration ( JMXExposed needs additional
> objects to be created ) , and of course I will not
> break your use cases.

You'll need an extended JNDIObjectReference implementation that makes usage of a provided MBeanServer and an DynamicMBeanComponentProvider array and you'll have to add the ctors of JMXExposing to JNDIExposing (still supporting a default ctor for your use case).

- Jörg

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email