[ 
https://issues.apache.org/jira/browse/XALANJ-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550638
 ] 

Michael Glavassevich commented on XALANJ-2343:
----------------------------------------------

Quite certain that I verified this a year ago before the serializer.jar from 
Xalan 2.7.1 went out in Xerces 2.9.0.

> [PATCH]: Issues with DOM L3 "entities" and "infoset" parameters.
> ----------------------------------------------------------------
>
>                 Key: XALANJ-2343
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2343
>             Project: XalanJ2
>          Issue Type: Bug
>          Components: DOM, Serialization
>            Reporter: Michael Glavassevich
>            Assignee: Brian Minchau
>             Fix For: 2.7.1
>
>         Attachments: ls-serializer-entities-infoset-patch.txt
>
>
> Setting the "infoset" parameter to true with the current code in SVN causes 
> the following exception when you try to serialize a document.
> java.lang.RuntimeException: The resource [  ] could not load: 
> java.lang.NumberFormatException: Listing</title> 
>        java.lang.NumberFormatException: Listing</title>
>       at org.apache.xml.serializer.CharInfo.<init>(CharInfo.java:302)
>       at org.apache.xml.serializer.CharInfo.<init>(CharInfo.java:173)
>       at org.apache.xml.serializer.CharInfo$1.run(CharInfo.java:465)
>       at java.security.AccessController.doPrivileged(Native Method)
>       at 
> org.apache.xml.serializer.CharInfo.getCharInfoBasedOnPrivilege(CharInfo.java:462)
>       at org.apache.xml.serializer.CharInfo.getCharInfo(CharInfo.java:526)
>       at org.apache.xml.serializer.ToStream.setOutputFormat(ToStream.java:603)
>       at 
> org.apache.xml.serializer.dom3.LSSerializerImpl.write(LSSerializerImpl.java:958)
> This exception occurs because the LSSerializer is trying to use the 
> OutputPropertiesFactory.S_KEY_ENTITIES for a different purpose than it was 
> intended to select whether or not to preserve entities in the document.  The 
> attached patch switches the code over to using a different non-conflicting 
> property name and also fixes a bug in handling the "infoset" property. 
> Setting the "infoset" property to false is supposed to have no effect, but 
> we're setting the properties anyways as if "infoset" were set to true.

-- 
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]

Reply via email to