[ 
https://issues.apache.org/jira/browse/CAMEL-20101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steven Dürrenmatt updated CAMEL-20101:
--------------------------------------
    Description: 
The *allowContextMapAll* query parameter is not present in the code, and the 
*allowTemplateFromHeader* parameter is used instead. By default the input 
context map is null if *allowTemplateFromHeader* is false, so no context will 
be passed to the Jolt transform at all.

Documentation for *allowContextMapAll* says: "Sets whether the context map 
should allow access to all details. By default only the message body and 
headers can be accessed", so Jolt transforms should have access to message 
headers by default. It is not clear whether this option should actually 
restrict the context map to headers, or just disallow the use of a context map.

  was:
The *allowContextMapAll* query parameter is not present and in the code, and 
the *allowTemplateFromHeader* parameter is used instead. By default the input 
context map is null if *allowTemplateFromHeader* is false, so no context will 
be passed to the Jolt transform at all.

Documentation for *allowContextMapAll* says: "Sets whether the context map 
should allow access to all details. By default only the message body and 
headers can be accessed", so Jolt transforms should have access to message 
headers by default. It is not clear whether this option should actually 
restrict the context map to headers, or just disallow the use of a context map.


> 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
>
> The *allowContextMapAll* query parameter is not present in the code, and the 
> *allowTemplateFromHeader* parameter is used instead. By default the input 
> context map is null if *allowTemplateFromHeader* is false, so no context will 
> be passed to the Jolt transform at all.
> Documentation for *allowContextMapAll* says: "Sets whether the context map 
> should allow access to all details. By default only the message body and 
> headers can be accessed", so Jolt transforms should have access to message 
> headers by default. It is not clear whether this option should actually 
> restrict the context map to headers, or just disallow the use of a context 
> map.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to