oscerd opened a new pull request, #25934:
URL: https://github.com/apache/camel/pull/25934

   Backport to `camel-4.22.x` of three consumer fixes already reviewed and 
merged on `main`. Each aligns a consumer with the `muteException` behaviour 
CAMEL-23651 established for the HTTP consumers: a route failure no longer hands 
the remote caller the exception class, message or stack trace.
   
   - CAMEL-24476: camel-mina - add a `muteException` consumer option (#25741, 
`7af3e74d`)
   - CAMEL-24477: camel-cxf - add a `muteException` consumer option (#25742, 
`fd4fd273`)
   - CAMEL-24478: camel-grpc - add a `muteException` consumer option (#25839, 
`3c998741`)
   
   **Behaviour change.** `muteException` defaults to `true`, so a consumer that 
used to echo the failure now returns a generic error. Set `muteException=false` 
to restore the old output. This matches what CAMEL-23651 did for the HTTP 
consumers.
   
   **Deviations from a straight cherry-pick**, both mechanical:
   
   - `MinaMuteExceptionTest` uses JUnit assertions instead of AssertJ. 
`camel-mina` has no assertj test dependency on this branch and its other 36 
test classes are JUnit, so adding one was the wrong trade for a backport.
   - The grpc commit on `main` carried an unrelated YAML DSL schema 
regeneration that removes `csimple` from the expression list. That hunk is left 
out; `csimple` is still valid on this branch.
   
   The upgrade-guide entries are not included: the guides for every line live 
on `main`.
   
   Built and tested per module on this branch (`camel-mina`, `camel-cxf-soap`, 
`camel-grpc`), including the new and touched tests. Catalog and DSL mirrors 
regenerated from this branch, so no `main`-only metadata leaks in.
   
   _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]

Reply via email to