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

   # Description
   
   [CAMEL-26157](https://issues.apache.org/jira/browse/CAMEL-26157): 
`ReactiveStreamsProducer` stored its dispatch callback (a lambda) in the 
`CamelReactiveStreamsCallback` header and never removed it, so after 
`to("reactive-streams:...")` the message carried that header.
   
   As proposed on the JIRA, the callback now calls the existing 
`ReactiveStreamsHelper.detachCallback` before `callback.done`, so the header is 
removed once the exchange is dispatched.
   
   Test: `BasicPublisherTest.testProducerRemovesCallbackHeader` sends through 
`to("reactive-streams:callback")` to a mock and checks the header is gone. It 
fails without the fix (the header is the `CamelPublisher` lambda) and passes 
with it. All 78 tests of camel-reactive-streams pass.
   
   # Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   # Tracking
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   # Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   
   - [x] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   # AI-assisted contributions
   
   - [x] If this PR includes AI-generated code, commits have proper 
co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR 
description identifies the AI tool used.
   
   This PR was prepared with the help of Claude (Anthropic), credited with a 
`Co-authored-by` trailer in the commit.


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