commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-335) XMLConfiguration: Can't disable attribute splitting
Date Sat, 27 Dec 2008 16:12:46 GMT


Oliver Heger commented on CONFIGURATION-335:

No, it was not. The implementation of attributes is different in the experimental branch:
attributes are not represented as Nodes, but each node has a map of attributes. Currently
there is no direct support for multiple values of an attribute. See also the {{NodeHandler}}
interface, which defines only a {{setAttributeValue()}} and a {{getAttributeValue()}} method.

For the experimental branch it makes certainly sense to redesign the whole splitting mechanism.
Looking back, it has caused us a lot of trouble, and I am wondering if it is worth the whole

> XMLConfiguration: Can't disable attribute splitting 
> ----------------------------------------------------
>                 Key: CONFIGURATION-335
>                 URL:
>             Project: Commons Configuration
>          Issue Type: Bug
>          Components: Format
>    Affects Versions: 1.5
>            Reporter: Sergey Vladimirov
>            Assignee: Oliver Heger
>             Fix For: 1.6
> My XML configuration has the following attribute:
> <some-element some-attribute="&#x0A;&#x0D;" />
> But XML Configuration is trying to split this string and trims it after splitting. I
don't need this behaviour, but setting setDelimiterParsingDisabled() just changing delimeter
to "|" and not disables attribute trimming.
> Need either to disable trimming/splitting if setDelimiterParsingDisabled() is set to
TRUE (incompatible change), or add something like setParseAttributesAsIs() that will prevent
attributes to be trimmed and splitted

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

View raw message