[ 
https://issues.apache.org/activemq/browse/CAMEL-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50547#action_50547
 ] 

Claus Ibsen edited comment on CAMEL-1450 at 3/13/09 11:38 PM:
--------------------------------------------------------------

Stephen, Hadrian

We cannot have imports to Spring .jars in camel-core.jar. We need to use 
reflection or other techniques to avoid having the import
import org.springframework.jmx.export.annotation.ManagedResource

You can for example use: camelContext.getClassResolver
to lookup the class at runtime.

This allows us to run Camel where people dont have Spring jars.

      was (Author: davsclaus):
    Stephen, Hadrian

We cannot have imports to Spring .jars in camel-core.jar. We need to use 
reflection or other techniques to avoid having the import
import org.springframework.jmx.export.annotation.ManagedResource

You can refer to it with its FQN name in the code:
org.springframework.jmx.export.annotation.ManagedResource mr = ...

You have to use: camelContext.getClassResolver
to lookup the class at runtime.

This allows us to run Camel where people dont have Spring jars.
  
> Add custom endpoints to camel jmx mbean server
> ----------------------------------------------
>
>                 Key: CAMEL-1450
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1450
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.6.0
>            Reporter: Stephen Mullins
>            Assignee: Hadrian Zbarcea
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: CAMEL-1450.patch
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Currently, when adding endpoints to the mbean server, all endpoints are 
> wrapped with ManagedEndpoint.  This does not allow for custom attributes or 
> operations to be exposed on the custom endpoints.  I would like the 
> InstrumentationLifecycleStrategy.onEndpointAdd() method to first check if the 
> endpoint is annotated with ManagedResource, if it is then register that 
> endpoint; if the endpoint is not annotated with ManagedResource then wrap it 
> with ManagedEndpoint and register.  This way all endpoints still get 
> registered but any custom attributes or operations will be exposed through 
> jmx.

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

Reply via email to