You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "David Valeri (JIRA)" <ji...@apache.org> on 2010/04/16 18:46:25 UTC
[jira] Updated: (CAMEL-2652) Allow camel-jetty to enable Jetty JMX
extensions
[ https://issues.apache.org/activemq/browse/CAMEL-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Valeri updated CAMEL-2652:
--------------------------------
Attachment: CAMEL-2652.patch
Proposed solution attached.
The solution allows the Camel JMX enable/disable capability to override the new configuration parameter and uses one instance of the Jetty MBeanContainer to prevent Jetty MBean name collisions when running multiple endpoints with JMX enabled in Jetty.
Note that the Karaf test changes were needed for:
1) Without depends plug-in version specified, m2Eclipse does not want to import the project.
2) camel-osgi feature was removed recently but the abstract test case still looks to load this feature causing all tests to fail.
> Allow camel-jetty to enable Jetty JMX extensions
> ------------------------------------------------
>
> Key: CAMEL-2652
> URL: https://issues.apache.org/activemq/browse/CAMEL-2652
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-jetty, karaf, tests
> Affects Versions: 2.3.0
> Reporter: David Valeri
> Attachments: CAMEL-2652.patch
>
>
> Provide a URL parameter to allow users to enable Jetty's JMX support when Camel JMX support is enabled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira