[ http://issues.apache.org/jira/browse/XMLBEANS-183?page=comments#action_12317437 ]
Neil Hyde commented on XMLBEANS-183: ------------------------------------ It seems you've attempted to fix this issue in version 2.0.0. But there is a problem in the new 2.0.0 code. In routine entitizeContent in Saver.java, the first loop which counts the number of chars that need escaping does not cater for ]]> strings. The net result is that ]]> strings don't get escaped unless the content also contains an ampersand char and/or a less than char and/or a bad char. If none of these other chars are present the routine exits at the first return before getting to the code which does the escaping. So any ]]> strings are left unchanged. > Invalid XML generated by XMLBeans > --------------------------------- > > Key: XMLBEANS-183 > URL: http://issues.apache.org/jira/browse/XMLBEANS-183 > Project: XMLBeans > Type: Bug > Versions: Version 1.0.3 > Environment: Windows XP, JDK 1.4 > Reporter: Neil Hyde > > The > character is not escaped by XMLBeans. This is not normally a problem > unless it's preceeded by ]], in which case the resultant ]]> string is deemed > to be markup (end of CDATA section). But what if ]]> is part of the content > I'm trying to output. How can I get XMLBeans to escape the > char in this > case, so that the resultant ]]> string is correctly interpreted as content > rather than markup when it's subsequently parsed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
