camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-8992) EIPs with Expression - Allow to detail those in jmx friendly information
Date Wed, 22 Jul 2015 17:48:05 GMT

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

Claus Ibsen resolved CAMEL-8992.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   2.16.0

> EIPs with Expression - Allow to detail those in jmx friendly information
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-8992
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8992
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, jmx
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.16.0
>
>
> The various EIPs have mbeans that exposes details about those processors. However when
they use expression/predicate we only have the actual created instances of those available
for JMX.
> That means they cannot reverse engineer or represent in a format that is better understood
by humans/jmx/toolings.
> For example
> {code}
>                 from("direct:start")
> .pollEnrich().simple("seda:${header.whereto}").timeout(1000).id("mysend")
>                     .to("mock:foo");
> {code}
> The simple expression on poll enrich becomes
> {code}
>         String uri = (String) mbeanServer.getAttribute(on, "Expression");
>         assertEquals("Simple: seda:${header.whereto}", uri);
> {code}
> Ideally we should have two information
> - the language used for the expression
> - the value as-is
> So we can show that its simple language with the value "seda:${header.whereto}"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message