[CAMEL-21153] camel-langchain4j-chat: split function calling feature

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.7.0
• Fix Version/s: 4.8.0
• Component/s: camel-ai, camel-langchain4j-chat, camel-langchain4j-tools
• Estimated Complexity: Unknown
• Assignee: Otavio Rodolfo Piske
• Reporter: Otavio Rodolfo Piske
• Created: 02/Sep/24 13:32
• Updated: 04/Sep/24 08:43
• Resolved: 03/Sep/24 11:05

Description

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:

1. The consumer routes are not reusable.
2. 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.
3. Having different producers associated with different tools.
4. It makes observability and route management more difficult and confusing
5. Because of similar route URLs and equal base URIs (i.e.; "langchain4j-chat:chatId").
6. If searching logs, management interfaces, by URL, then multiple routes might match.
7. Error handling is more complex
8. Having the tools feature as part of the chat component, also makes it a bit confusing and hard to find.

Issue Links

• links to: GitHub Pull Request #1208
• links to: GitHub Pull Request #15396
• links to: GitHub Pull Request #15411
• links to: GitHub Pull Request #15414