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 2003/02/10 15:27:33 UTC
DO NOT REPLY [Bug 16927] New: -
cdata-section-elements yields many 32 char CDATA sections
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=16927>.
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=16927
cdata-section-elements yields many 32 char CDATA sections
Summary: cdata-section-elements yields many 32 char CDATA
sections
Product: XalanJ2
Version: 2.4
Platform: PC
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Xalan-CmdLine
AssignedTo: xalan-dev@xml.apache.org
ReportedBy: taylor_cowan@yahoo.com
When I specify cdata-section-elements ( within the xsl:output tag ) ='script'
the resulting output divides the original CDATA into many CDATA tags. I
noticed that they are all 32 chars long. The XSLT processor should take the
original CDATA and transfer it to the output unmodified. It seems odd that it
chooses 32 characters as a max length. Here is some example output from Xalan
2.4.1 (note, the original JavaScript was formatted in a typical way with only 1
CDATA):
<script language="javascript"><![CDATA[
var loggedInEmploye]]><![CDATA[e = null; // Describes the ID of]]><![CDATA[ the
employee logged in
var tp6]]><![CDATA[PublishDate = null;
var accessLe]]><![CDATA[vel = null;
var employee = null;]]><![CDATA[ // Describes the id of the empl]]><![CDATA
[oyee in the drop down
var global]]><![CDATA[Status = null; // Describes the ]]><![CDATA[status
selected in the status li]]><![CDATA[st
var projectStatus = null; // ]]><![CDATA[Describes the status of the proj]]><!
[CDATA[ect that is currently selected
f]]><![CDATA[unction setBeanData(loggedInEmpl]]><![CDATA
[oyee,tp6PublishDate,acsLvl,emp,s]]><![CDATA[ts)
{