[jira] Resolved: (CXF-2195) InstrumentationManagerImpl is doing too many things at a time -- would be much better if registering mbeans and exposing over a port are separated

["Daniel Kulp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-2195.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.2
                   2.1.6


We added a bunch of new flags and such for obtaining the JMX MBeanServer and connections and such to make this much more flexible.

> InstrumentationManagerImpl is doing too many things at a time -- would be much better if registering mbeans and exposing over a port are separated
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2195
>                 URL: https://issues.apache.org/jira/browse/CXF-2195
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.1.5
>            Reporter: Celal Ziftci
>             Fix For: 2.1.6, 2.2.2
>
>
> Currently InstrumentationManagerImpl class is doing a little bit too much in terms of jmx support.
> I'm trying to make use of it in an enterprise world, and the registering of cxf mbeans and exposing of the mbeanserver over a protocol are bundled into the InstrumentationManagerImpl class.
> Ideally, we would like to have these separated, so that we can still use cxf's built-in mechanism of registration of mbeans to a specific mbeanserver. But then the job of exposing the MBeanServer should be left to the end-user.
> We have an infrastructure to do authentication and authorization on jmx connectors, which requires us to use our own connectors.
> And what we would like is from cxf is: cxf registers its mbeans for endpoints, managedbus etc to a specified mbeanserver.
> Once it is done, we can expose that mbeanserver over our own connectors, and do proper authentication and authorization.
> Please let me know if you would like me to provide more concrete examples. A good example where this feature I'm asking for is implemented is Spring framework, where they have a concept of "MBeanExporter", which only exports to a given MBeanServer (but doesn't try to start a connector).
> Currently, this is really blocking me from using the InstrumentationManagerImpl class.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.