Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -262,6 +262,31 @@ As a consequence, the generated Endpoint DSL header accessors on
* `linkType()` -> `jiraLinkType()`
* `minutesSpent()` -> `jiraMinutesSpent()`

=== camel-mongodb-gridfs - potential breaking change

The Exchange header values exposed by `GridFsConstants` have been renamed to follow the standard
Camel naming convention, bringing `camel-mongodb-gridfs` in line with the parent `camel-mongodb`
component (`MongoDbConstants.OPERATION_HEADER = "CamelMongoDbOperation"`). The Java field names
are unchanged, so routes referencing the constants symbolically
(e.g. `GridFsConstants.GRIDFS_OPERATION`, `GridFsConstants.GRIDFS_OBJECT_ID`) continue to work
without modification. However, routes that set or read these headers using the raw string values
must be updated:

* `gridfs.operation` -> `CamelGridFsOperation`
* `gridfs.metadata` -> `CamelGridFsMetadata`
* `gridfs.chunksize` -> `CamelGridFsChunkSize`
* `gridfs.objectid` -> `CamelGridFsObjectId`
* `gridfs.fileid` -> `CamelGridFsFileId`

As a consequence, the generated Endpoint DSL header accessors on `GridFsHeaderNameBuilder`
have been renamed accordingly:

* `gridfsOperation()` -> `gridFsOperation()`
* `gridfsMetadata()` -> `gridFsMetadata()`
* `gridfsChunksize()` -> `gridFsChunkSize()`
* `gridfsObjectid()` -> `gridFsObjectId()`
* `gridfsFileid()` -> `gridFsFileId()`

== Upgrading from 4.14.2 to 4.14.3

=== camel-tika
Expand Down