commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CONFIGURATION-358) subset returned from HierarchicalINIConfiguration has unexpected property names
Date Fri, 09 Jan 2009 07:06:59 GMT

    [ https://issues.apache.org/jira/browse/CONFIGURATION-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662257#action_12662257
] 

Oliver Heger commented on CONFIGURATION-358:
--------------------------------------------

You are right that the dot is used as property delimiter for historic reasons. When XML configurations
were introduced it was decided to use the dot as delimiter between XML element names to resemble
the way properties files are typically constructed. Now it became a standard for hierarchical
configurations, and we probably have to stick with it.

I don't know whether it makes sense to disable parsing of the property delimiter in an ExpressionEngine.
This is a central part of what an expression engine does. And it restricts using of a hierarchical
configuration dramatically. For instance, using a hierarchical INI configuration you still
want to access single properties with a key like {{section.property}}. You could not do that
if property delimiters are not recognized. So changing the property delimiter to a character
that is not contained in the keys makes sense to me, but not disabling it at all.

I agree that the documentation about the escaping syntax is hidden in the XML section. If
we restructure it to apply to all hierarchical configurations, can we then close this ticket?

> subset returned from HierarchicalINIConfiguration has unexpected property names
> -------------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-358
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-358
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: Documentation, Format
>    Affects Versions: 1.6
>            Reporter: Charles Honton
>             Fix For: 1.6
>
>         Attachments: TestHierarchicalINIConfiguration.java, TestHierarchicalINIConfiguration.java,
TestHierarchicalINIConfiguration.java
>
>
> With the following ini file
> # comment
> property.1 = g1
> property.2 : g2
> [section]
> property.1 = l1
> HierarchicalINIConfiguration properly creates two sections: null and "section".  However,
the subsets from this configuration do not have the expected property names.
> The global subset contains the following name=value pairs:
> property..1=g1
> property..2=g2
> section.property..1=l1
> The "section" subset contains the following name=value pairs:
> property..1=g1
> I expected the global subset to contain:
> property.1=g1
> property.2=g2
> I expected the "section" subset to contain:
> property.1 = l1

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message