[
https://issues.apache.org/jira/browse/CONFIGURATION-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661999#action_12661999
]
Charles Honton commented on CONFIGURATION-358:
----------------------------------------------
The dot escaping documentation is buried in a section about XML tags - not INI
files. As you said, more hints required.
A bigger question to me is why the dot escaping is required at all. It appears
to be an implementation relic of property file parsing. I finally got the
results I wanted with
DefaultExpressionEngine expressionEngine = new
DefaultExpressionEngine();
expressionEngine.setPropertyDelimiter("\000");
HierarchicalINIConfiguration rc= new
HierarchicalINIConfiguration();
rc.setExpressionEngine(expressionEngine);
An aside, how about a method on the ExpressionEngine to turn off property
delimiting?
> 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.
