Andrea Cosentino created CAMEL-23575:
----------------------------------------

             Summary: camel-mongodb-gridfs: align Exchange header constant 
names with Camel naming convention
                 Key: CAMEL-23575
                 URL: https://issues.apache.org/jira/browse/CAMEL-23575
             Project: Camel
          Issue Type: Improvement
          Components: camel-mongodb-gridfs
            Reporter: Andrea Cosentino
            Assignee: Andrea Cosentino
             Fix For: 4.21.0, 4.18.3, 4.14.8


The Exchange header constants in {{GridFsConstants}} ({{camel-mongodb-gridfs}}) 
use raw string values that do not follow the {{Camel<Component><Field>}} naming 
convention used across the rest of the component catalog — notably the parent 
{{camel-mongodb}} component, where {{MongoDbConstants.OPERATION_HEADER}} is 
{{CamelMongoDbOperation}}. Rename the string *values* only — keep the Java 
field names unchanged so routes/code referencing the constants symbolically 
continue to work:

* {{GridFsConstants.GRIDFS_OPERATION}}: {{gridfs.operation}} -> 
{{CamelGridFsOperation}}
* {{GridFsConstants.GRIDFS_METADATA}}: {{gridfs.metadata}} -> 
{{CamelGridFsMetadata}}
* {{GridFsConstants.GRIDFS_CHUNKSIZE}}: {{gridfs.chunksize}} -> 
{{CamelGridFsChunkSize}}
* {{GridFsConstants.GRIDFS_OBJECT_ID}}: {{gridfs.objectid}} -> 
{{CamelGridFsObjectId}}
* {{GridFsConstants.GRIDFS_FILE_ID_PRODUCED}}: {{gridfs.fileid}} -> 
{{CamelGridFsFileId}}

Consistent with the same alignment applied to camel-lucene (CAMEL-23509), 
camel-jgroups (CAMEL-23510), camel-jgroups-raft (CAMEL-23511), and camel-cxf 
(CAMEL-23526). Affects 4.21.0 (current main), 4.18.x, and 4.14.x — the 
constants are identical on all three branches.

h4. Tasks
* Change the five constant string values in {{GridFsConstants}}; keep Java 
field names.
* Audit usages of the literal string values across {{camel-mongodb-gridfs}} and 
tests for consistency.
* Regenerate component metadata, catalog, and endpoint DSL.
* Add a {{=== camel-mongodb-gridfs}} entry to 
{{docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc}} (and 
the matching 4.18 / 4.14 upgrade-guide files when backporting), mirroring the 
camel-cxf entry (symbolic references unaffected; routes using the literal 
string keys must be updated).

_Reported by Claude Code on behalf of Andrea Cosentino._



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

Reply via email to