[
https://issues.apache.org/jira/browse/XMLBEANS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wing Yew Poon closed XMLBEANS-272.
----------------------------------
Resolution: Won't Fix
This has nothing to do with entities per se. XMLBeans has an algorithm that
deteremines when to use a CDATA section when marshalling to xml. In 2.x, Cezar
has provided finer-grained control over the use of CDATA sections. This won't
be back-ported to 1.x.
> Limit on Number of Character Encoded Entitities (NCRs) Inside Element
> ---------------------------------------------------------------------
>
> Key: XMLBEANS-272
> URL: https://issues.apache.org/jira/browse/XMLBEANS-272
> Project: XMLBeans
> Issue Type: Bug
> Components: XmlObject
> Affects Versions: Version 1.0.4
> Environment: Windows 2000, JRocket version: BEA WebLogic JRockit(TM)
> 1.4.2_08 JVM R24.5.0-61
> Reporter: Henri Hein
>
> Steps:
> Add a text element like this:
> output.addText("’ “ ” … „ „
> ");
> Output:
> <Text><![CDATA[&#8217; &#8220; &#8221; … „
> „]]></Text>
> Add a text element like this:
> output.addText("’ “ ” … „ #8222;
> ");
> Output:
> <Text>&#8217; &#8220; &#8221; &#8230; &#8222;
> #8222;</Text>
> Expect:
> The first case should be
> <Text>&#8217; &#8220; &#8221; &#8230; &#8222;
> &#8222;</Text>
> The characters are all valid NCRs. See
> http://www.w3.org/Talks/1999/0830-tutorial-unicode-mjd/all.htm
> It doesn't matter which one I un-escape, or if I delete it completely. What
> seems to matter is the _count_ of NCRs inside the element.
> There were some discussion in the archives about similar issues.
> Appearently, XMLBeans decides to use CDATA sometimes using rules that are not
> entirely clear. It seems arbitrary to use the count of escaped characters,
> and this particular behaviour is decidedly unexpected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
