Why log component in camel behaves differently based on the order of attributes ?

Solution Verified - Updated -

Issue

  • Just realised that the log component behaves differently based on the order of the attributes.
  • Is logName attribute expected before loggingLevel ? This works for me :
<log message="derive characteristics request: ${body}" logName="aaa.bbb.ccc.dddd.eee" loggingLevel="DEBUG" />
  • Whereas this doesnot work
<log message="aggregated derivation request input: ${body}" loggingLevel="DEBUG" logName="aaa.bbb.xxx.ccc.dddd.eee"/>
  • After I swapped the order of logName and loggingLevel in the about log component, it worked.
  • If Yes, then is it applicable for all other components as well ?

Environment

  • Red Hat JBoss Fuse
    • 6.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.