atiaomar1978-hub opened a new pull request, #26027:
URL: https://github.com/apache/camel/pull/26027

   ## Summary
   
   The core CAMEL-23928 API (first-class tool-calling options on 
`AgentConfiguration` and the `withAiServicesCustomizer()` escape hatch wired 
through `AbstractAgent.configureBuilder()`) is already on `main` since #24492. 
This PR completes the ticket by adding behavioral test coverage and component 
documentation so the feature is discoverable and verified end-to-end.
   
   ## Changes
   
   - **Unit tests** (`AgentConfigurationToolCallingBehaviorTest`): verify 
hallucinated tool name recovery, max tool round-trip enforcement, tool 
execution error handler + compensation, and customizer-driven 
`beforeToolExecution` wiring via `AgentWithoutMemory`.
   - **Integration tests** (`LangChain4jAgentAiServicesCustomizerTest`): verify 
the same options through the `langchain4j-agent` component with 
`agentConfiguration` beans and Camel route tools.
   - **Documentation** (`langchain4j-agent-component.adoc`): document 
first-class tool-calling methods and the AiServices customizer escape hatch for 
options like `beforeToolExecution`, `afterToolExecution`, and 
`toolSearchStrategy`.
   - **Catalog mirror** regenerated for the updated component documentation.
   
   ## Testing
   
   ```bash
   mvn test -pl 
components/camel-ai/camel-langchain4j-agent-api,components/camel-ai/camel-langchain4j-agent
 -am \
     
-Dtest=AgentConfigurationToolCallingBehaviorTest,LangChain4jAgentAiServicesCustomizerTest
 \
     -DfailIfNoTests=false -Ddevelocity.buildCache.local.enabled=false
   ```
   
   All 6 new tests pass locally.
   
   ## JIRA
   
   https://issues.apache.org/jira/browse/CAMEL-23928
   
   ---
   _AI-generated PR description on behalf of atiaomar1978-hub_


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