On 2010-10-05 16.54, Niclas Hedhman wrote:
At the moment the "Properties -> ConfigurationEntity" translator only
handles 'discrete' configuration values, i.e. it can't be a Property
of a complex Value type, nor pointer to another Configuration.
I think that for 1.3 we should probably try to define more complex
configuration options, so it can more easily map to other system's
configuration, which are often enough XML based or large fluent APIs
with a lot of nesting.
This is a Request-for-Request-for-Proposals, so to speak. I have no
immediate requirements and hope people could point out what we should
do in this area.
It would be entirely possible for us to support an alternative XML
format as well as the properties format for configuration defaults. That
would seem like the simplest way to do it.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
