[
https://issues.apache.org/jira/browse/XERCESJ-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879811#comment-13879811
]
John Phoenix commented on XERCESJ-1626:
---------------------------------------
It now appears that the long comment may not have been the issue. I added some
more configuration data to the version of the XML file without long comments
and the corruption issue returned. I have resolved this by breaking the
configuration down into a number of smaller files.
The original file that showed the issue was about 36k long, which doesn't seem
very long to me, though it is longer than the default buffer size for the
parser, I believe.
> Java SAX parser returns corrupted data from an XML file containing a long
> comments
> ----------------------------------------------------------------------------------
>
> Key: XERCESJ-1626
> URL: https://issues.apache.org/jira/browse/XERCESJ-1626
> Project: Xerces2-J
> Issue Type: Bug
> Components: SAX
> Environment: Windows XP jdk1.7.0_45
> Reporter: John Phoenix
> Priority: Minor
>
> I am using SAX parser with validation enabled (though this doesn't seem to
> make any difference) to read a configuration file for my application. I have
> placed a number of explanatory comments into the XML file to remind me how to
> create the configuration. Some of these are around 30 lines in length. With
> the comments present, the configuration data returned by the SAX parser
> contains some corrupted elements, though these do not immediately follow the
> comment. With the long comments removed, the data appears to be read
> correctly.
> I can supply XML and XSD files that display the issue, and even a NetBeans
> project that shows the problem if that would help.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
