jamesnetherton opened a new issue, #8857: URL: https://github.com/apache/camel-quarkus/issues/8857
Some features were added to the langchain4j-agent component recently. We should add coverage here, primarily to check that they work in native mode. **1. Structured output** Test the two endpoint options: - `outputClass` — derives a JSON schema from a Java POJO class - `jsonSchema` — loads a JSON schema from a classpath resource, file, or inline string **2. `AgentConfiguration` auto-provisioning mode for langchain4j-agent** All existing `langchain4j-agent` integration tests create pre-built `Agent` beans via CDI `@Produces` methods and reference them with `agent=#beanName`. The alternative — and simpler — approach where users set `agentConfiguration` on the endpoint and Camel automatically creates an `AgentWithMemory` or `AgentWithoutMemory` based on whether a `ChatMemoryProvider` is present is not currently tested. **3. MCP server configuration** The `langchain4j-agent` component supports declarative MCP server definitions via multi-value endpoint URI options (e.g. `mcpServer.myServer.transportType=http&mcpServer.myServer.url=...`). This allows users to configure MCP servers without writing CDI producer methods. Currently only pre-built `McpClient` beans are tested (via the stdio transport with `npx`). The inline `mcpServer.*` configuration path — which involves runtime materialization of `LangChain4jMcpServerDefinition` objects and transport construction — is untested. -- 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]
