Andrea Cosentino created CAMEL-23579:
----------------------------------------
Summary: camel-pdf - align Exchange header constant names with
Camel naming convention
Key: CAMEL-23579
URL: https://issues.apache.org/jira/browse/CAMEL-23579
Project: Camel
Issue Type: Improvement
Components: camel-pdf
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
Fix For: 4.21.0
The PDF header constants in
{{org.apache.camel.component.pdf.PdfHeaderConstants}} use hyphenated string
values that do not follow the Camel naming convention. Read by {{PdfProducer}}:
* {{DECRYPTION_MATERIAL_HEADER_NAME = "decryption-material"}} - decryption
password material
* {{PROTECTION_POLICY_HEADER_NAME = "protection-policy"}} - PDF encryption
policy
* {{PDF_DOCUMENT_HEADER_NAME = "pdf-document"}} - PDDocument for append
* {{FILES_TO_MERGE_HEADER_NAME = "files-to-merge"}} - file list for merge
Rename to {{CamelPdf<Name>}} ({{CamelPdfDecryptionMaterial}},
{{CamelPdfProtectionPolicy}}, {{CamelPdfDocument}}, {{CamelPdfFilesToMerge}}).
h3. Fix shape
Rename the *string value* of each producer-read header constant to
{{Camel<Component><Name>}}; keep the Java field name unchanged so routes that
reference the constants symbolically continue to compile and run. Update tests
that use the literal string values; regenerate component catalog JSON and docs;
add an upgrade-guide entry in {{camel-4x-upgrade-guide-4_21.adoc}} (and
matching 4_18 / 4_14 for backports where the component existed in those
branches).
h3. References
* Tracker: CAMEL-23577
* Precedent (rename pattern): CAMEL-23526 (camel-cxf)
* Alternative pattern (HeaderFilterStrategy approach): CAMEL-23532
(camel-vertx-websocket / camel-atmosphere-websocket / camel-iggy)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
