Andrea Cosentino created CAMEL-23532:
----------------------------------------
Summary: camel-vertx-websocket / camel-atmosphere-websocket /
camel-iggy - use dedicated HeaderFilterStrategy aligned with sibling components
Key: CAMEL-23532
URL: https://issues.apache.org/jira/browse/CAMEL-23532
Project: Camel
Issue Type: Improvement
Components: camel-atmosphere-websocket, camel-vertx-websocket
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
Fix For: 4.21.0, 4.18.3, 4.14.8
The inbound consumers in {{camel-vertx-websocket}},
{{camel-atmosphere-websocket}} and {{camel-iggy}} map externally supplied
key/value data (WebSocket query/path parameters; Iggy message user-headers)
into the Camel message header map without a dedicated {{HeaderFilterStrategy}},
unlike sibling consumer components aligned in CAMEL-23222 / CAMEL-23506 /
CAMEL-23507 / CAMEL-23515.
Align these components with that pattern:
* {{camel-vertx-websocket}}: add a {{VertxWebsocketHeaderFilterStrategy}} and
apply it in {{VertxWebsocketConsumer.populateExchangeHeaders()}} before mapping
query/path params.
* {{camel-atmosphere-websocket}}: add a header filter strategy and apply it in
{{WebsocketConsumer}} before mapping query-map entries.
* {{camel-iggy}}: add a header filter strategy and apply it in
{{IggyFetchRecords}} before copying message user-headers.
Use existing sibling implementations (e.g. {{CoAPHeaderFilterStrategy}},
{{KafkaHeaderFilterStrategy}}) as the reference. Include tests and an
upgrade-guide note, as done for the sibling components.
Scope note: {{camel-iggy}} does not exist on the 4.14.x line - its change
applies to main + 4.18.x only.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
