Child pages
  • MVEL Component
Skip to end of metadata
Go to start of metadata

MVEL Component

Available as of Camel 2.12

The mvel: component allows you to process a message using an MVEL template. This can be ideal when using Templating to generate responses for requests.

Maven users will need to add the following dependency to their pom.xml for this component:

    <!-- use the same version as your Camel core version -->

URI format


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, ?option=value&option=value&...


Message Headers

The mvel component sets a couple headers on the message.

MVEL Context

Camel will provide exchange information in the MVEL context (just a Map). The Exchange is transfered as:

Hot reloading

The mvel template resource is, by default, hot reloadable for both file and classpath resources (expanded jar). If you set contentCache=true, Camel will only load the resource once, and thus hot reloading is not possible. This scenario can be used in production, when the resource never changes.

Dynamic templates

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 JMSReplyTo header).

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:

  setHeader("CamelMvelTemplate").constant("@{\"The result is \" + request.body * 3}\" }").
  • No labels