oscerd commented on PR #29832:
URL: https://github.com/apache/camel/pull/29832#issuecomment-6912199268
Pushed `CAMEL-26837: The inputExpression docs show the safe pattern and say
what a custom input gives up` (ea568aa43d5d):
- **Doc example** (please change): the example now builds the input from a
verified exchange property and puts the body under its own key
(`Map.of("subject", exchange.getProperty("verifiedSubject"), "order",
exchange.getMessage().getBody())`), in Java with an `ExpressionAdapter` and in
the XML and YAML tabs through a small application `Expression` class, and a
`WARNING:` says the body comes from the sender and must not supply identity or
role fields, pointing to the "Authorizing an identity" section.
- **Credential headers**: the same paragraph now says the default envelope
withholds `Authorization`, `Proxy-Authorization`, `Cookie` and `Set-Cookie`,
and that a custom expression gets none of that protection.
- **Single vs batch**: documented rather than changed: for a single exchange
the expression runs on the live exchange (a header it sets stays), in batch
mode on a copy.
- **`getIn().setBody`** duplicate line dropped (gnodet-bot thread).
- **Imports** instead of FQCNs in `OpaInputExpressionTest`.
- Per-item batch outcomes: left as is, fail-closed for the whole batch as
documented.
Catalog doc copy regenerated; `OpaInputExpressionTest` green.
_Claude Code on behalf of oscerd_
--
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]