jamesnetherton commented on issue #8768:
URL: https://github.com/apache/camel-quarkus/issues/8768#issuecomment-4740747956
Instead of annotations, I wonder if a pure config-driven approach would be
better? It might be a bit verbose, but there are some advantages like being
able to support any DSL and being able to potentially tweak some aspects of the
config at runtime.
Example:
```yaml
quarkus:
camel:
langchain4j:
tools:
send-email:
route-id: send-email
description: "Sends a transactional email to a user"
parameters:
to:
type: string
description: "Recipient email address"
required: true
subject:
type: string
description: "Email subject line"
required: true
```
Then we could implement a `ToolProvider` bean which can read the config,
invoke the Camel route and return the result. It'll either get used
automatically by QL4J. Or if there are multiple tool providers, you can
explicitly declare it:
```java
@RegisterAiService(toolProviderSupplier = CamelToolSupplier.class)
public interface SupportAiService {
}
```
WDYT?
--
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]
