camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4988) Problems with Simple language
Date Thu, 23 Feb 2012 10:59:49 GMT


Claus Ibsen commented on CAMEL-4988:

How often do you have a <bean> of type String? Whats the point? I have never seen the
need for that.
> Problems with Simple language
> -----------------------------
>                 Key: CAMEL-4988
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.0
>         Environment: Standalone application with Spring context and routes defined in
>            Reporter: Diego
> If you don't use a simple expresion that falls back to the SimpleBackwardsCompatibleParser,
the simple language doesn't seem to work. If I override the start and end token with an explicit
definition of the simplelanguage everything works well.
>   <bean id="simple" class="org.apache.camel.language.simple.SimpleLanguage">
>       <constructor-arg name="functionStartToken" value="${"/>
>       <constructor-arg name="functionEndToken" value="}"/>
>   </bean> 
> It seems that org.apache.camel.language.simple.SimpleExpressionParser.SimpleExpressionParser(String)
fails to create an expression because startToken and endToken are "automagically" changed
for strange Strings. It seems that when exchange.getContext().resolveLanguage("simple") tries
to resolve the languaje it doesn't use the default construtor and injects a strange start
and end token in the constructor SimpleLanguage(String functionStartToken, String functionEndToken).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message