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

Andrea Cosentino resolved CAMEL-23591.
--------------------------------------
    Resolution: Fixed

> camel-mail - align consumer-side dispatch header constant names with Camel 
> naming convention
> --------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-23591
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23591
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-mail
>            Reporter: Andrea Cosentino
>            Assignee: Andrea Cosentino
>            Priority: Minor
>             Fix For: 4.21.0
>
>
> {{MailConstants}} defines consumer-side dispatch headers read by 
> {{MailConsumer.processCommit}} after the route runs to decide mail-folder 
> dispatch:
> * {{MAIL_DELETE = "delete"}}
> * {{MAIL_MOVE_TO = "moveTo"}}
> * {{MAIL_COPY_TO = "copyTo"}}
> Companion to CAMEL-23522 (JavaMail session property gating) in the same 
> component. Rename to {{CamelMailDelete}} / {{CamelMailMoveTo}} / 
> {{CamelMailCopyTo}}.
> 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)

Reply via email to