Background
The initial implementation of externalized FpML coding scheme validation relied on a custom Java implementation (ValidateFpMLCodingSchemeImpl) and injection via the CdmRuntimeModule. This approach created a hidden dependency on Java-specific logic that was not transparent within the Rune-DSL model itself.
We are migrating the core validation logic directly into the DSL, allowing the model to define its own validation behavior natively. Note that while the validation logic is now model-driven, the cdm.base.staticdata.codelist.LoadCodeList function must still be implemented natively by each code-generator as it requires File System access (outside the scope of Rune-DSL).
This change simplifies the Java runtime footprint and ensures a consistent validation contract across all supported languages.
Proposal
Migrate the coding scheme validation logic from Java to Rune-DSL and decommission the legacy Java infrastructure (classes and module bindings).
Compatibility
Functionally backward-compatible.
While specific internal Java classes and runtime bindings are removed, the logical validation results remain identical for downstream users.
Release
Next available 7.x milestones.
Additional Context
No response
Background
The initial implementation of externalized FpML coding scheme validation relied on a custom Java implementation (
ValidateFpMLCodingSchemeImpl) and injection via theCdmRuntimeModule. This approach created a hidden dependency on Java-specific logic that was not transparent within the Rune-DSL model itself.We are migrating the core validation logic directly into the DSL, allowing the model to define its own validation behavior natively. Note that while the validation logic is now model-driven, the
cdm.base.staticdata.codelist.LoadCodeListfunction must still be implemented natively by each code-generator as it requires File System access (outside the scope of Rune-DSL).This change simplifies the Java runtime footprint and ensures a consistent validation contract across all supported languages.
Proposal
Migrate the coding scheme validation logic from Java to Rune-DSL and decommission the legacy Java infrastructure (classes and module bindings).
Compatibility
Functionally backward-compatible.
While specific internal Java classes and runtime bindings are removed, the logical validation results remain identical for downstream users.
Release
Next available 7.x milestones.
Additional Context
No response