[
https://issues.apache.org/jira/browse/CAMEL-21153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-21153:
-----------------------------------------
Issue Type: Improvement (was: Bug)
> camel-langchain4j-chat: split function calling feature
> ------------------------------------------------------
>
> Key: CAMEL-21153
> URL: https://issues.apache.org/jira/browse/CAMEL-21153
> Project: Camel
> Issue Type: Improvement
> Components: camel-ai, camel-langchain4j-chat, camel-langchain4j-tools
> Affects Versions: 4.7.0
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Fix For: 4.8.0
>
>
> Currently, our implementation of function calling requires potential
> consumers of those routes to be directly linked to those producers. This
> means that there is an exclusive 1-to-MANY relationship between the producer
> and the consumers.
> This implementation brings limitations and problems:
> # The consumer routes are not reusable.
> # Each of them is directly linked to the producer. Which means that it makes
> it much harder to link them to more than one producer.
> # Having different producers associated with different tools.
> # It makes observability and route management more difficult and confusing
> # Because of similar route URLs and equal base URIs (i.e.;
> "langchain4j-chat:chatId").
> # If searching logs, management interfaces, by URL, then multiple routes
> might match.
> # Error handling is more complex
> # Having the tools feature as part of the chat component, also makes it a bit
> confusing and hard to find.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
