CAMEL-25259: design - DSL extensions, the mini DSLs features add to route files - #27265

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

This matches the experience we had with CAMEL-24977, CAMEL-25049 and CAMEL-25138. Evaluation and batching already worked across DSLs through the shared semantic language. Adding question declarations to Java and XML required separate work on the authoring APIs, parsing, metadata and loading behavior, with tests to keep them consistent with YAML.

I support having an annotated model in the feature module as the common definition. A useful goal would be that adding a question option means defining its shape, documentation and default once, with the different DSLs and tooling deriving their support from that definition. Generating schemas and catalog entries would be a good first step, while keeping shared or generated readers, writers and Java builders as the broader direction.

One distinction worth exploring is Java authoring versus parsing existing Java source. We could have the fluent Java API build the same declaration model used by XML and YAML, while deciding separately how the converter reads that Java code.

Our implementation also gives us some useful cases to try against the model: named Choice criteria versus ordered Score levels, numeric options containing property placeholders, and declarations shared across resources. We ran into these during the Java/XML work, so they would help us discover what the model and common loading hooks need to express.

Could we use semantic as the first end-to-end example, preserving its existing syntax and behavior, and see how much DSL-specific code we can replace with the shared model? That would give us a concrete basis for shaping the extension mechanism.

AI-generated by Codex on behalf of luigidemasi.

ℹ️ CI did not run targeted module tests.

🔁 8 tests passed only after a retry on JDK 25 (8 retried attempts)

⚙️ View full build and test results