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

   Step 1: Create the new camel-ai-tool module with AiToolSpec, AiToolRegistry, 
consumer endpoint, and full tests. No changes to existing modules.
   
   # Description
   
   ## Summary
   
   Create the new `camel-ai-tool` module with the unified AI tool abstraction 
layer:
     - `AiToolSpec` — vendor-neutral tool descriptor (name, description, 
parameters, tags)
     - `AiToolRegistry` — central registry for discovering and managing AI tools
     - `AiToolConsumer` — endpoint that registers Camel routes as AI-callable 
tools
     - Full unit test coverage
   
   No changes to existing modules in this PR.
   
    ## Roadmap
   Technical design details : design/aiTool.adoc file
   
   This work is split into several sequential PRs to keep reviews focused:
   
     - [x] **Step 1** (this PR): Create the new `camel-ai-tool` module with 
`AiToolSpec`, `AiToolRegistry`, consumer endpoint, and full tests. No changes 
to existing modules.
     - [ ] **Step 2**: Wire `camel-langchain4j-agent` producer to read tools 
from `AiToolRegistry` instead of the old cache, with upgrade guide entry.
     - [ ] **Step 3**: Wire `camel-spring-ai-chat` producer to discover tools 
from `AiToolRegistry`, with upgrade guide entry.
     - [ ] **Step 4**: Wire `camel-langchain4j-tools` producer to read from 
`AiToolRegistry`, keeping the agentic loop intact.
     - [ ] **Step 5**: Deprecate `camel-langchain4j-tools` consumer side and 
remove `camel-spring-ai-tools` entirely, with upgrade guide entries for both.
     - [ ] **Step 6**: Add tool support to `camel-openai`. Resolve tools from 
`AiToolRegistry` and implement the dispatch loop
     (separate Jira issue).
   
   


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