davsclaus commented on PR #27079:
URL: https://github.com/apache/camel/pull/27079#issuecomment-5908626324
A few doc/discoverability additions so users find Switch next to Choice:
1. **EIP index**: add a Switch row to the *Message Routing* table in
`core/camel-core-engine/src/main/docs/modules/eips/pages/enterprise-integration-patterns.adoc`,
right after the `xref:choice-eip.adoc[Content-Based Router]` row (the
`ContentBasedRouterIcon.gif` image fits). For example: *How do we route a
message to a fixed endpoint by the literal value of a single selector, like a
decision table?*
2. **AI patterns page** (`eips/pages/ai-patterns.adoc`):
- Add `xref:switch-eip.adoc[Switch]` to the *Router / Dispatch* row next
to Choice and Dynamic Router.
- In the *AI and Agent Integration* table, add a row like *Classify /
Intent routing*. A `semantic` choice question returns a category string, which
Switch dispatches by literal case. That is the natural pairing with
camel-semantic. A short YAML example in `switch-eip.adoc` showing a `semantic`
selector would help too.
3. **Cross-linking Choice ↔ Switch**:
- `switch-eip.adoc` already points to Choice, but `choice-eip.adoc` has
no link back. Please add a short "Use Switch when you dispatch on the literal
value of one expression" note.
- Catalog term lookup uses the `aliases` on the model `@Metadata`. Choice
has `aliases = { "router", "dispatch" }`, while `SwitchDefinition` has none.
Suggest something like `aliases = { "decision-table", "lookup-table", "case"
}`, so a search for those terms finds Switch instead of only Choice.
_Claude Code on behalf of davsclaus_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
