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

   Fixes [CAMEL-26064](https://issues.apache.org/jira/browse/CAMEL-26064).
   
   When the route of an as2 `server/listen` or `receipt/receive` consumer 
failed, the consumer threw an `HttpException` with the message of the exception 
of the route, which HttpCore sent to the partner as the body of the HTTP 500. 
platform-http, undertow and camel-http have `muteException` for this, true by 
default in platform-http and undertow.
   
   **Changes**
   - `AS2Configuration`: the `muteException` option (consumer), `true` by 
default. The 500 then only says "Failed to process AS2 message" (or "Failed to 
process AS2 receipt"); `false` gives the message of the exception as before.
   - `AS2Consumer` and `AS2AsyncMDNConsumer` use it.
   - Regenerated: the configurers, `as2.json` and its catalog copy, and the 
endpoint DSL.
   - Docs: a sentence in the usage of the as2 page, and the upgrade guide 4.24, 
as the default changes what the partner gets.
   
   **Tests**
   - `AS2ServerManagerIT.sendEditMessageToFailingProcessorTest` now expects the 
muted text, and fails without the change; 
`sendEditMessageToFailingProcessorNotMutedTest` checks the message of the 
exception with `muteException=false`.
   - The 13 unit tests and the 112 integration tests of camel-as2 pass. One 
full run had a port bind failure at the start of a route of 
`AS2AsyncMDNServerManagerIT`; that class passed when run again, and so did the 
next full run.
   
   Found while adding the catalog body types of as2 (CAMEL-24961).
   
   _Claude Code on behalf of davsclaus_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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