[
https://issues.apache.org/jira/browse/CAMEL-20101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dürrenmatt updated CAMEL-20101:
--------------------------------------
Description:
According to documentation, one should set the *allowContextMapAll* query
parameter to *true* to allow contextual transforms. However in the code this
parameter is not present and the *allowTemplateFromHeader* parameter is used
instead.
Moreover documentation says "By default only the message body and headers can
be accessed", but only the message body would be passed as input to the Jolt
transform. It is not clear whether this option should restrict the context map,
or just allow to use a context map that has full access to the current Exchange
and CamelContext.
was:
According to documentation, one should set the *allowContextMapAll* query
parameter to *true* to allow contextual transforms. However in the code this
parameter is not present and the *allowTemplateFromHeader* parameter is used
instead.
Moreover documentation says "By default only the message body and headers can
be accessed", but only the message body would be passed as input to the Jolt
transform.
> camel-jolt - query parameter allowContextMapAll is ignored
> ----------------------------------------------------------
>
> Key: CAMEL-20101
> URL: https://issues.apache.org/jira/browse/CAMEL-20101
> Project: Camel
> Issue Type: Bug
> Components: camel-jolt
> Affects Versions: 3.14.10, 3.18.8, 3.20.8, 3.21.2, 4.0.2
> Reporter: Steven Dürrenmatt
> Priority: Minor
>
> According to documentation, one should set the *allowContextMapAll* query
> parameter to *true* to allow contextual transforms. However in the code this
> parameter is not present and the *allowTemplateFromHeader* parameter is used
> instead.
> Moreover documentation says "By default only the message body and headers can
> be accessed", but only the message body would be passed as input to the Jolt
> transform. It is not clear whether this option should restrict the context
> map, or just allow to use a context map that has full access to the current
> Exchange and CamelContext.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
