On Sat, Dec 31, 2005 at 04:04:47PM +, Chris Burdess wrote:
Mark Wielaard wrote:
You are running some test-suites from time to time on the xml
parsers. If these are free then I would like to add them to
builder.classpath.org so regressions (or better conformance results) are
Hi Chris,
On Tue, 2005-12-27 at 20:03 +, Chris Burdess wrote:
Please test the new XML parser on as many weird and wonderful XML
sources as you can, and report any problems to me either by mail or
Bugzilla - I will try to deal with them before release, or we can
revert to aelfred2 again if
Mark Wielaard wrote:
You are running some test-suites from time to time on the xml
parsers. If these are free then I would like to add them to
builder.classpath.org so regressions (or better conformance results) are
automatically tracked. How much space do they need and is it difficult
to
Chris Burdess wrote:
We discovered over IRC that there is a major problem with XML parsing using
the StAX driver, caused by a bug in BufferedInputStream. I'm therefore
reverting the default XML parser to aelfred2 until this is resolved.
Further investigation revealed that the problem was more
Chris == Chris Burdess [EMAIL PROTECTED] writes:
Chris Note that the behaviour of BufferedInputStream is correct - but
Chris that of BufferedReader is not.
Please file a PR for this.
Tom
___
Classpath mailing list
Classpath@gnu.org
Hi
We discovered over IRC that there is a major problem with XML parsing using
the StAX driver, caused by a bug in BufferedInputStream. I'm therefore
reverting the default XML parser to aelfred2 until this is resolved.
The bug is in both gnu.xml.stream.XMLInputStreamReader and
Chris Burdess wrote:
As I understand it, the problem can occur when the position in the buffer is
near the end. If the mark is set at position 2047 in the buffer, then we read
2 bytes and reset, then refill() will have been called and the position is
actually reset to position 2047 in the new
7 matches
Mail list logo
