Joe Luo created CAMEL-10529:
-------------------------------

             Summary: The "exchange" keyword in LogEIP was incorrectly 
evaluated as a Camel Exchange type even without "${ }"
                 Key: CAMEL-10529
                 URL: https://issues.apache.org/jira/browse/CAMEL-10529
             Project: Camel
          Issue Type: Bug
          Components: camel-language
    Affects Versions: 2.17.0
            Reporter: Joe Luo


I have a very simple camel route:
{code}
<camelContext id="camel" xmlns="http://camel.apache.org/schema/blueprint";>
        <route>
            <from uri="timer://foo?delay=2s&amp;repeatCount=2"/>
            <setBody>
                <constant>hello Camel!</constant>
            </setBody>
            <log message="exchange is triggered"/>
        </route>
    </camelContext>
{code}
Then I am getting the following error:
{code}
16:09:32,724 | WARN | #3 - timer://foo | TimerConsumer | 232 - 
org.apache.camel.camel-core - 2.17.0.redhat-630187 | Error processing exchange. 
Exchange[ID-jluomac-54194-1480090135878-3-4]. Caused by: 
[org.apache.camel.RuntimeCamelException - 
org.apache.camel.component.bean.MethodNotFoundException: Method with name: is 
triggered not found on bean: Exchange[ID-jluomac-54194-1480090135878-3-4] of 
type: org.apache.camel.impl.DefaultExchange]
org.apache.camel.RuntimeCamelException: 
org.apache.camel.component.bean.MethodNotFoundException: Method with name: is 
triggered not found on bean: Exchange[ID-jluomac-54194-1480090135878-3-4] of 
type: org.apache.camel.impl.DefaultExchange
{code}
It looks like it was incorrectly evaluated as a Camel Exchange type for some 
reason.
Furthermore, it is only causing the problem when it is in the beginning of the 
LogEIP message. If it is not, it works fine. For instance, following line will 
cause problem:
{code}
<log message="exchange is triggered"/>
{code}
But this will work:
{code}
<log message="The exchange is triggered"/>
{code}
As long as you are not placing the keyword "exchange" in the beginning of the 
LogEIP message, it will be fine.



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

Reply via email to