chore: Improve exchange pattern documentation to clarify behavior - #25033
Merged
Conversation
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
davsclaus
force-pushed
the
quick-fix/exchange-pattern-docs
branch
2 times, most recently
from
July 22, 2026 17:15
78614dd to
11ada52
Compare
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
davsclaus
force-pushed
the
quick-fix/exchange-pattern-docs
branch
from
July 22, 2026 17:16
11ada52 to
b31713c
Compare
gnodet
approved these changes
Jul 22, 2026
gnodet
left a comment
gnodet
left a comment
Contributor
There was a problem hiding this comment.
Clean, well-written documentation improvement that clarifies exchange pattern behavior — the "How It Works" sections are technically accurate and address recurring user confusion about MEP being a component-level contract vs. processor-level control.
CI note: Build 25 fails because the generated catalog copies of event-message.adoc and requestReply-eip.adoc under catalog/camel-catalog/src/generated/resources/ were not regenerated and committed. Running mvn clean install -Dquickly should regenerate them.
Pre-existing observation (not introduced by this PR): In event-message.adoc line 20, xref:ROOT:jms-component.adoc[File] links to JMS but displays "File" — should be xref:ROOT:file-component.adoc[File]. Could be fixed opportunistically while editing this file.
LGTM! 👍
This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.
Claude Code on behalf of Guillaume Nodet
… link Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
Contributor
Author
|
Thanks @gnodet for the review! Addressed both items:
|
Contributor
|
🧪 CI tested the following changed modules:
🔬 Scalpel shadow comparison — Scalpel: 485 tested, 27 compile-only — current: 483 all testedMaveniverse Scalpel detected 512 affected modules (current approach: 483).
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Claude Code on behalf of davsclaus
Improves the exchange pattern documentation to clarify how
InOnlyandInOutactually work, addressing recurring confusion from users on the mailing list.Changes:
exchange-pattern.adoc— Added "How Exchange Pattern Works" section explaining it is a component-level contract, does not affect processors likesetBody, and clarifying async vs sync component behavior (seda/jms fire-and-forget vs direct same-thread)requestReply-eip.adoc— Added "How It Works" section explainingInOutis a contract with the endpoint, not a flow control mechanismevent-message.adoc— Added "How It Works" section forInOnlywith the same clarificationsevent-message.adoc— Fixed pre-existing broken xref link (was linking to JMS with "File" label instead of File component)event-message.adocandrequestReply-eip.adocPrompted by discussion with Raymond Meester on the Camel users mailing list.
Test plan
mvn clean install -Dquickly)🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com