You are viewing a plain text version of this content. The canonical link for it is here.

Posted to j-dev@xerces.apache.org by bu...@apache.org on 2001/06/18 17:19:53 UTC

[Bug 2194] - Xerces2: problems using OneCharReader

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2194

*** shadow/2194	Fri Jun 15 10:06:37 2001
--- shadow/2194.tmp.19464	Mon Jun 18 08:19:53 2001
***************
*** 35,37 ****
--- 35,45 ----
  would actually be a deficiency if they DIDN'T buffer the data.  IMHO, the 
  current implementation of wrapping streams and readers needs to be replaced with 
  a more robust solution to this problem.
+ 
+ ------- Additional Comments From pkuzel@sun.com  2001-06-18 08:19 -------
+ I think that the OneCharReader should take InputStream. Buffered InputStream
+ will not throw IOException caused by invalid encoding of characters that are
+ read ahead. mark() and reset() should fit rest of bill.
+ If InputSource contains a Reader it should be used directly (on caller
+ responsibility, without autodetection) so InputStream is adequate.
+ Crimson's XmlReader looks better coded in this area.
\ No newline at end of file

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org