[CONFIGURATION-605] XMLConfiguration drops configuration key immediately following one whose value contains a comma

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10
• Fix Version/s: 2.0
• Component/s: Format

Environment

$ uname -a
Linux 4.1.2-2-ARCH #1 SMP PREEMPT Wed Jul 15 08:30:32 UTC 2015 x86_64 GNU/Linux

$ java -version
openjdk version "1.8.0_45"
OpenJDK Runtime Environment (build 1.8.0_45-b14)
OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)

• Assignee: Unassigned
• Reporter: Emil Lundberg
• Created: 20/Jul/15 13:02
• Updated: 24/Mar/16 20:21
• Resolved: 03/Aug/15 19:49

Description

The following XML document:

StringBuilder sb = new StringBuilder("<configuration>");}}
sb.append("<test1>a,b,c</test1>");
sb.append("<test2>a</test2>");
sb.append("<test3></test3>");
 sb.append("<test4>a,b\\,b,c</test4>");
sb.append("</configuration>");

when passed into XMLConfiguration#load(Reader) and then to ConfigurationUtils#toString(Configuration), comes out like this:

test1=[a, b, c]
test3=
test4=[a, b,b, c]

I'm assuming this is a bug.

I've found two workarounds to this:

1. Inserting any character between the test1 and test2 tags, i.e. <test1>a,b,c</test1> <test2>a</test2>
2. Calling setDelimiterParsingDisabled(true) on the XMLConfiguration before loading the document

For reproduction with a minimal example and some additional test cases, see this GitHub repo. I also posted this as a question on Stack Overflow before posting here.