[
https://issues.apache.org/jira/browse/CAMEL-9672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182675#comment-15182675
]
Claus Ibsen commented on CAMEL-9672:
------------------------------------
Thanks yeah JMX tests should go in the management directory. Maybe you can work
on an unit test there as it would be great to have one to ensure this bug do
not re-appear.
> ClassCastException with interceptFrom
> -------------------------------------
>
> Key: CAMEL-9672
> URL: https://issues.apache.org/jira/browse/CAMEL-9672
> Project: Camel
> Issue Type: Bug
> Components: camel-core, jmx
> Affects Versions: 2.16.2
> Reporter: Stephan Siano
> Priority: Minor
> Fix For: 2.16.3, 2.17.0
>
> Attachments: 0001-Relax-type-restriction-on-ManagedFilter.patch
>
>
> If a statement like
> {code:java}
> interceptFrom().when(simple("${header.foo} == 'bar'")).to("mock:intercepted");
> {code}
> is available in a route builder with JMX enabled the startup will fail in
> Camel 2.16.2 (and the current 2.17-SNAPSHOT) with a ClassCastException in
> line 310 of DefaultManagementObjectStrategy.
> The generated processor is a FilterProcessor, but the resulting definition is
> a WhenDefinition not a FilterDefinition.
> The reason is that CAMEL-8992 introduced a too precise class check for this.
> The attached patch relexes the class constraint on the definition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
