davsclaus opened a new pull request, #85:
URL: https://github.com/apache/camel-jbang-examples/pull/85

   Rung 8 of the ladder from CAMEL-24808: AI, under `ai/`.
   
   - `mcp-server` (new): two routes exposed as MCP tools, `stock_level` by SKU 
and `order_status` by order id, on `http://localhost:8080/mcp` with nothing but 
`camel.server.mcp-*` properties to switch the server on. The README shows an 
`mcp.json` for a coding agent and the `curl` handshake. The Citrus test opens 
an MCP session over HTTP, extracts the session id and calls both tools.
   - `langchain4j-chat` (replaces `genai-observability`, now YAML): the chat 
model is a bean built through its LangChain4j builder (`builderClass`, 
`builderMethod`) from properties, and a local Ollama model started with `camel 
infra run ollama` writes the shipping notification for each of the three 
orders; the reply and its token counts are logged. The observability part is a 
"Try changing" step with `--observe`. The Citrus test starts Ollama on a side 
port, waits until the model is pulled and verifies a notification; it pulls a 
2.1 GB model and runs it on the CPU, so it is a local check and not in the CI 
matrix (`ciSkip` in the metadata). How cumbersome the builder bean is went into 
CAMEL-24820.
   - `docling-langchain4j-rag`: compose file gone, the README uses `camel infra 
run docling ollama` and the properties match the services' fixed ports and the 
`granite4:3b` model the infra pulls.
   - `openai-pii-redaction` stays as it is.
   
   MCP server test passes locally and in CI; the chat test passes locally. 
Catalog regenerated (40 examples).
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj


-- 
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]

Reply via email to