atiaomar1978-hub commented on PR #25228:
URL: https://github.com/apache/camel/pull/25228#issuecomment-5160223090

   _AI-generated comment on behalf of 
[atiaomar1978-hub](https://github.com/atiaomar1978-hub)_
   
   @davsclaus Good question — I looked through Croway's langchain4j-related 
work and there is **no prior PR that exposed LangChain4j's 
`executeToolsConcurrently()`** on `AgentConfiguration`. That wiring is new in 
this PR (CAMEL-23952).
   
   What Croway **did** do in the same area (and what this PR builds on):
   
   | Ticket / PR | Author | What it did |
   |---|---|---|
   | [CAMEL-16861](https://issues.apache.org/jira/browse/CAMEL-16861) | @Croway 
| MCP client support for `camel-langchain4j-agent` (`CompositeToolProvider`, 
endpoint MCP servers, ITs). Concurrent tool mode helps when the LLM calls 
multiple MCP + Camel route tools in one turn. |
   | [CAMEL-23621](https://issues.apache.org/jira/browse/CAMEL-23621) / #23535 
| @Croway | Filter tool-argument headers to declared parameters only (prevents 
header leakage between tools). |
   | [CAMEL-21937](https://issues.apache.org/jira/browse/CAMEL-21937) / #23807 
| @davsclaus | Fix `stop()` EIP leaking `ROUTE_STOP` across **parallel** tool 
invocations in `camel-langchain4j-tools` (`LangChain4jToolStopEipTest`). |
   | [CAMEL-23704](https://issues.apache.org/jira/browse/CAMEL-23704) / #24062 
| @k-krawczyk | Isolated `ExchangeHelper.createCopy()` per tool in 
`camel-langchain4j-tools`. |
   | [CAMEL-23944](https://issues.apache.org/jira/browse/CAMEL-23944) / #24992 
| @gnodet | Same exchange-copy isolation in `camel-langchain4j-agent` route 
tools — **prerequisite** for safe concurrent execution. |
   
   **This PR** adds the LangChain4j-side parallel dispatch 
(`withExecuteToolsConcurrently()` / optional `Executor`), a Camel-managed 
executor when none is supplied, and `AgentConfiguration.duplicate()` so shared 
registry beans are not mutated. The exchange-copy safety net was already in 
place from CAMEL-23944.
   
   So if you had MCP integration in mind — yes, that's Croway's piece. The 
concurrent *execution toggle* itself is new here.


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