With our current schema definitions, property substitution is only valid for XML fields. Using a property like "$
{foo:1000}
" on a config value with an xsd:integer type will fail XML validation. To address this, we need to do two things:
1) Add new simpleType definitions to the core SY schema that allow properties to be substituted for integer, long, and boolean types.
2) Replace any use of integer and long in the component schemas to use propInteger and propLong respectively. NOTE: we should not replace boolean elements with propBoolean at this point since the tooling won't be able to handle this for 0.8.
This should be all schema changes with no code changes required. I have already created the simple types and updated a test in core/config to get the ball rolling. At this point, it's just a matter of updating all the component schemas to use the propInteger and propBoolean types.
https://github.com/kcbabo/core/tree/xsdprops
https://github.com/kcbabo/core/commit/0d7fae05e707c95d888590522b1d650190ec4fdb
|