Andrea Cosentino created CAMEL-24896:
----------------------------------------
Summary: camel-chunk: align Exchange header constant names with
Camel naming convention
Key: CAMEL-24896
URL: https://issues.apache.org/jira/browse/CAMEL-24896
Project: Camel
Issue Type: Improvement
Components: camel-chunk
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
Fix For: 4.18.5, 4.23.0, 4.22.2
The camel-chunk component defines its Exchange header constant *values* without
the standard "Camel" prefix:
{code}
ChunkConstants: CHUNK_RESOURCE_URI = "ChunkResourceUri"
CHUNK_TEMPLATE = "ChunkTemplate"
{code}
Every sibling template engine already follows the convention
(CamelFreemarkerResourceUri/Template, CamelVelocityResourceUri/Template,
CamelThymeleafResourceUri/Template, CamelMvelResourceUri/Template,
CamelJteResourceUri/Template, CamelStringTemplateResourceUri/Template), as do
the other transform components (camel-jolt, camel-jslt, camel-jsonata,
camel-xslt, camel-sql-stored). camel-mustache is the only other remaining
outlier and is tracked under a companion issue.
Header values in the Camel* namespace are governed by the default
HeaderFilterStrategy (which filters Camel* / camel* at message boundaries),
which keeps component headers consistent and prevents them from crossing
transport boundaries. The unprefixed chunk values fall outside that filter. The
affected header reads are already gated behind the non-default
allowTemplateFromHeader option.
Proposed change, following the header naming alignment done under CAMEL-23577:
* Rename the constant *values* to CamelChunkResourceUri / CamelChunkTemplate.
Keep the Java field names (CHUNK_RESOURCE_URI, CHUNK_TEMPLATE) unchanged for
source compatibility.
* Update the component docs and regenerate the catalog + endpoint DSL.
* Add an upgrade-guide entry (potential breaking change) documenting the header
value rename.
* Backport to 4.22.x and 4.18.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
