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
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.
ChunkAvailable as of Camel 2.15 The chunk: component allows for processing a message using a Chunk template. This can be ideal when using Templating to generate responses for requests. Maven users will need to add the following dependency to their <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-chunk</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency> URI formatchunk:templateName[?options] Where templateName is the classpath-local URI of the template to invoke. You can append query options to the URI in the following format, Options
Chunk component will look for a specific template in themes folder with extensions .chtml or .cxml. If you need to specify a different folder or extensions, you will need to use the specific options listed above. Chunk ContextCamel will provide exchange information in the Chunk context (just a
Dynamic templatesCamel 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.
SamplesFor example you could use something like: from("activemq:My.Queue"). to("chunk:template"); To use a Chunk template to formulate a response for a message for InOut message exchanges (where there is a If you want to use InOnly and consume the message and send it to another destination you could use: from("activemq:My.Queue"). to("chunk:template"). to("activemq:Another.Queue"); It's possible to specify what template the component should use dynamically via a header, so for example: from("direct:in"). setHeader(ChunkConstants.CHUNK_RESOURCE_URI).constant("template"). to("chunk:dummy"); An example of Chunk component options use: from("direct:in"). to("chunk:file_example?themeFolder=template&themeSubfolder=subfolder&extension=chunk"); In this example Chunk component will look for the file file_example.chunk in the folder template/subfolder. The Email SampleIn this sample we want to use Chunk templating for an order confirmation email. The email template is laid out in Chunk as: Dear {$headers.lastName}, {$headers.firstName} Thanks for the order of {$headers.item}. Regards Camel Riders Bookstore {$body} |