davsclaus opened a new issue, #99: URL: https://github.com/apache/camel-jbang-examples/issues/99
Three examples run, but fail on every message or at startup, because they need something the example catalog does not say. Their READMEs say it, but `camel run --example` and the example browsers only show `metadata.json`. - **contracts/openapi-client** needs `contracts/openapi-server` running first. Run alone, every order fails with "Connect to http://localhost:8080 failed". - **ai/langchain4j-chat** needs the model `granite4:3b` pulled into Ollama. With only the `ollama` infra running, every exchange fails with "model `granite4:3b` not found" (93 of 93 in a test run). Neither the run nor the infra pulls it. - **ai/openai-pii-redaction** needs `OPENAI_API_KEY`. Without it, the start fails with "Property with key [env:OPENAI_API_KEY] ... returned null value". Suggestion: let `metadata.json` say what an example needs beyond `infraServices`, so tools can say so before the run. `needs` is already free text for the README tables; a structured form would let tools check it. For example: - another example running first: `"requires": ["contracts/openapi-server"]` - a model to pull: `"models": ["granite4:3b"]` - environment variables: `"env": ["OPENAI_API_KEY"]` Tools (`camel run --example`, the example browsers) can then say "start openapi-server first", "run ollama pull granite4:3b", or "set OPENAI_API_KEY" before the run, or check it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
