If there aren't any sequencers configured, then there isn't any sequencing going on. This could be a potential bug with the parsing of the initial content files.
Is there any chance you could attach your xml file (with commas in it) ?
This is a full example where lead and body text are split by the comma in the text. I tested providing the strings as attribute and sub element but there is no difference in the handling.
<?xml version="1.0" encoding="UTF-8"?>
<sites jcr:primaryType="wmod:section" title="Sites">
<mst jcr:primaryType="wmod:section" title="Times">
<section jcr:primaryType="wmod:section" title="News">
<section jcr:primaryType="wmod:section" title="Politics">
title="Story with commas in the text lead and body text"
lead="Lead text in attribute, split with a comma.">
<body>Body text in sub element, also split by the comma.</body>
I am using 3.1.1.Final. Not sure what other info is useful. As I said, I have a very simple repository config, not specifying any sequencers.
The story type is defined like this:
[wmod:content] > nt:unstructured, mix:referenceable, mix:created, mix:lastModified
[wmod:story] > wmod:content
Had a look at the code and it seems we always use the "," character as an indicator of multi-valued properties and split accordingly.
Can you please log an enhancement request and we'll try to see if there's another way of handling/specifying them in the XML format.