You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@xalan.apache.org by bu...@apache.org on 2002/04/16 12:05:21 UTC

DO NOT REPLY [Bug 8157] New: - Too many CDATA

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8157>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8157

Too many CDATA

           Summary: Too many CDATA
           Product: XalanJ2
           Version: 2.3
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Xalan
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: hkj@bording.dk


Xalan sometimes divides a value into multiple CDATA sections, e.g. 
<value>POWERCORD</value> is divided into </value><![CDATA[POWERCOR]]><![CDATA
[D]]></value> and this is done to optimize perfermance in some way.

This is not very useful when you need to search the output or having humans 
read it. So therefore it would be nice to be able to turn off this optimization 
be setting a flag or property of some kind. Even though performance is reduced 
it is sometimes very useful to be able to search the output immidiately even 
though you have to wait longer for the output to process.