...
Where templateName is the classpath-local URI of the template to invoke; or the complete URL of the remote template (eg: file://folder/myfile.vm
).
Options
Option | Default | Description |
|---|---|---|
loaderCache | true | Velocity based file loader cache |
contentCache | false | New option in Camel 1.4. Cache for the resource content when its loaded. |
Hot reloading
The velocity template resource is by default hot reloadable for both file and classpath resources (expanded jar). Setting the contentCache=true then Camel will only load the resource once, and thus hot reloading is not possible. This scenario can be used in production usage when the resource never changes.
Samples
For example you could use something like
...
| Code Block |
|---|
from("activemq:My.Queue").
to("velocity:com/acme/MyResponse.vm").
to("activemq:Another.Queue");
|
And to use content cache, eg. for production usage where the .vm template never changes:
| Code Block |
|---|
from("activemq:My.Queue").
to("velocity:com/acme/MyResponse.vm?contentCache=true").
to("activemq:Another.Queue");
|
And a file based resource:
| Code Block |
|---|
from("activemq:My.Queue").
to("velocity:file://myfolder/MyResponse.vm?contentCache=true").
to("activemq:Another.Queue");
|
...