camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1769) ExpressionDefinition can not be able to render in web console
Date Fri, 27 Aug 2010 12:00:40 GMT

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

Claus Ibsen commented on CAMEL-1769:
------------------------------------

We are trimming camel-web and therefore the groovy editor is either removed or moved to an
optional component.

If we remove the groovy editor then this bug can be closed with wont fix.
However there are a good chance for this, as the camel team can't maintain the groovy editor
and its not much in demand.

> ExpressionDefinition can not be able to render in web console
> -------------------------------------------------------------
>
>                 Key: CAMEL-1769
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1769
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Xueqiang Mi
>            Priority: Minor
>             Fix For: Future
>
>
> When add a route with groovy expression, camelcontext can't provide some readable information
to render the route.
> For example, when adding a route, the ExpressionDefinition can convert header("foo").isEqualTo("bar")
to {header(foo) == bar}, which can be used in groovy renderer easily. But when we save the
route with the sentence {header(foo) == bar}, the ExpressionDefinition can not convert it
to a readable expression this time. It only reply a {Groovy[GroovyRoute$_configure_closure1@9c7307]}
when request the expression.
> The ExpressionDefinition do the following convertions:
>           java fluent expression  ------------->  groovy style experssion
>           groovy style expression ------------>  un-readable built-in groovy closure
> So we can't render the groovy expression in web console. Maybe we should store some expressions
when receiving a route with groovy expressions.

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


Mime
View raw message