[
http://team.ops4j.org/browse/QI-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370#comment-17370
]
Paul Merlin commented on QI-350:
--------------------------------
Sure, this could work well for configuration defaults in properties files.
> Nested Configurations
> ---------------------
>
> Key: QI-350
> URL: http://team.ops4j.org/browse/QI-350
> Project: Qi4j
> Issue Type: New Feature
> Reporter: Paul Merlin
> Fix For: 2.1 - Simply Productive!
>
>
> This was shortly discussed on the mailing-list about a year ago :
> 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.
> On 2010-10-05 18:42, Rickard Oberg wrote:
> > 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.
> I create this issue to keep a track of the general idea and raise the subject
> up.
> I suspect I have a use case but I will work a little bit more on it before
> coming back here.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://team.ops4j.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
