The following comment has been added to this issue:

     Author: David Bertoni
    Created: Thu, 16 Sep 2004 9:13 AM
       Body:
Your code is violating the design of the interface you're implementing.  If you have 
more data than the maximum size of the buffer the parser provides, you are responsible 
for buffering the remaining data somewhere and feeding it to parser as it requests it.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/XERCESC-1271?page=comments#action_53149

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESC-1271

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESC-1271
    Summary: Problems parsing large XML strings
       Type: Bug

     Status: Resolved
   Priority: Major
 Resolution: INCOMPLETE

    Project: Xerces-C++

   Assignee: 
   Reporter: Fred Preston

    Created: Fri, 10 Sep 2004 5:00 AM
    Updated: Thu, 16 Sep 2004 9:13 AM
Environment: n/a

Description:
When testing with large XML strings, xerces falls over when the size of the XML 
exceeds the 16 * 1024 limit that is hardwired into the XMLReader.hpp file 
(375:kCharBufSize        = 16 * 1024).  Would it be possible to dynamically allocate 
space for this and other buffers (fCharBuf and fCharSizeBuf) and then to extend them 
using the realloc function when necessary.  This also applies to the fRawByteBuf 
buffer that is also limited in size.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to