Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.
Available as of Camel 2.12
Maven users will need to add the following dependency to their
Where templateName is the classpath-local URI of the template to invoke; or the complete URL of the remote template (eg: file://folder/myfile.mvel).
You can append query options to the URI in the following format,
The mvel component sets a couple headers on the message.
Camel will provide exchange information in the MVEL context (just a
The mvel template resource is, by default, hot reloadable for both file and classpath resources (expanded jar). If you set
Camel provides two headers by which you can define a different resource location for a template or the template content itself. If any of these headers is set then Camel uses this over the endpoint configured resource. This allows you to provide a dynamic template at runtime.
For example you could use something like
To use a MVEL template to formulate a response to a message for InOut message exchanges (where there is a
To specify what template the component should use dynamically via a header, so for example:
To specify a template directly as a header the component should use dynamically via a header, so for example: