[CXF-3992] Making JMX instrumentation manager configurable using some bus properties

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.1
• Fix Version/s: 2.5.2
• Component/s: Management
• Estimated Complexity: Unknown
• Assignee: Akitoshi Yoshida
• Reporter: Akitoshi Yoshida
• Created: 21/Dec/11 17:12
• Updated: 07/Feb/12 21:50
• Resolved: 22/Dec/11 12:03

Description

In some cases, for example, on an OSGi container having the JMX mbean server service running, with CXF 2.5.0 and up, there is no need in explicitly configuring the instrumentation manager bean. In other cases, the instrumentation manager bean may need to be explicitly configured. Previously, this meant that an instance of the InstrumentationManagerImpl bean must be configured. And in this case, there was some issue in the consistent association between the bus and its configured instrumentation manager instance, as initially another instrumentation manager instance is initially assigned to the bus.

In order to solve this problem and at the same time to simplify the configuration, this patch introduces a mechanism to directly configure the instrumentation bean using some specific bus properties.

Here is a sample:

<cxf:bus bus="mybus">
  <cxf:properties>
    <entry key="bus.jmx.enabled" value="true"/>
    <entry key="bus.jmx.threaded" value="false"/>     
    <entry key="bus.jmx.daemon" value="false"/>
    <entry key="bus.jmx.JMXServiceURL" value="service:jmx:rmi:///jndi/rmi://localhost:9914/jmxrmi" />
  </cxf:properties>
</cxf:bus>

Property bus.jmx.prop corresponds to property prop of the InstrumentationManager bean.