luigidemasi opened a new pull request, #281: URL: https://github.com/apache/camel-examples/pull/281
Adds a Camel YAML coordinator and four Camel A2A specialists for a car-rental support example. A request such as “Will it rain in Lisbon, and how much is an SUV for five days?” selects both weather and cost specialists through batched semantic questions, calls them in parallel, and combines their accepted replies. Semantic checks drive bounded retries and explicit clarification or review responses. The example uses `camel-semantic`, `camel-typesafe-ai`, `camel-a2a`, `camel-openai`, and the Split and Switch EIPs. A small Camel-agnostic Java bean handles selection and reply policy. The README covers Jev, Laya, Julia-1 and Tev1 decision services, OpenAI-compatible reply generation, Maven/JBang startup, and Camel TUI inspection. Bash and PowerShell launchers share a local environment file with a committed template and ignored credentials. Inspired by Kevin Dubois's [first agent-routing article](https://www.kevindubois.com/2026/09/23/routing-agents-with-jev-and-laya-adding-system-one-decisions-to-quarkus-langchain4j/) and [follow-up on multi-intent requests and fan-out](https://www.kevindubois.com/2026/10/01/routing-with-jev-and-langchain4j-agentic-part-2-the-real-api-multi-intent-requests-and-fan-out/). Validation: - `mvn -B -ntp -pl semantic-agent-routing verify`: 20 fixture tests passed; one opt-in live provider evaluation skipped. Normal tests require no API keys or model downloads. - Bash syntax and Bash/PowerShell environment-loading checks passed with dummy credentials; PowerShell checks ran on Linux without starting Windows processes. Requires Camel 4.23.0-SNAPSHOT. The opt-in evaluation records decision quality separately from orchestration tests. A single-specialist request skips merging and the whole-request completeness check, so an accepted response does not guarantee that the decision service selected every relevant specialist. -- 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]
