THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
You can append query options to the URI in the following format, ?option=value&option=value&...
Options
| Div | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
| ||||||||||||
| Wiki Markup | ||||||||||||
| {div:class=confluenceTableSmall}
|| Option || Default || Description ||
| {{contentCache}} | {{false}} | Cache for the resource content when its loaded. \\ Note : as of *Camel 2.9* cached resource content can be cleared via JMX using the endpoint's {{clearContentCache}} operation. ||
| {{delimiterStart}} | {{null}} | *Since Camel 2.11.1*, configuring the variable start delimiter |
| {{delimiterStop}} | {{null}} | *Since Camel 2.11.1*, configuring the variable end delimiter |
{div} |
Headers
Camel will store a reference to the resource in the message header with key, org.apache.camel.stringtemplate.resource. The Resource is an org.springframework.core.io.Resource object.
...
Camel will provide exchange information as attributes (just a java.util.Map) to the string template. The Exchange is transfered as:
| Div | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
| ||||||||||||||||||
| Wiki Markup | ||||||||||||||||||
| {div:class=confluenceTableSmall}
|| key || value ||
| {{exchange}} | The Exchange itself. |
| {{headers}} | The headers of the In message. |
| {{camelContext}} | The Camel Context. |
| {{request}} | The In message. |
| {{in}} | The In message. |
| {{body}} | The In message body. |
| {{out}} | The Out message (only for InOut message exchange pattern). |
| {{response}} | The Out message (only for InOut message exchange pattern). |
{div} |
Since Camel 2.14, you can define the custom context map by setting the message header "CamelStringTemplateVariableMap" just like the below code.
...