davsclaus opened a new pull request, #27265: URL: https://github.com/apache/camel/pull/27265
[CAMEL-25259](https://issues.apache.org/jira/browse/CAMEL-25259) This is a design proposal for discussion; there is no code. It adds `design/dsl-extensions.adoc`. A feature can add a mini DSL of its own to route files; camel-semantic's questions are the first. Today its shape is described three times by hand, as YAML schema stubs, a StAX parser and a Java builder, and the catalog and tooling don't know it exists. The proposal makes such *DSL extensions* first class: - **One model.** An annotated model in the feature's own module is the single source of truth. - **Generated artifacts.** The YAML schema fragment, the XSD and a new catalog kind (`dsl-extensions/<name>.json`, with samples per DSL) are generated from that model. - **Runtime SPI** (CAMEL-25257). Tooling can detect, extract and write declarations without running anything. - **Tools learn from the catalog only:** - jbang dependency detection; - the converter; - the validator, including checks of `ref:` references; - the MCP catalog tools; - completion in the source editor. One goal is that agentic coding with a local model, one that knows nothing about semantic, gets the same contract, sample and validation loop that already works for EIPs. The doc ends with open questions: naming, where YAML schema fragments are merged, XML namespaces, the Java DSL side (the replay surface of the parser) and versioning. _Claude Code on behalf of davsclaus_ 🤖 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]
