|
It also behaves the same way with Xerces 2.7 I have also found that very occasionally
it works as I would expect but mostly the events do not get fired unless I
close the connection causing eof in the input stream. From: Gary Hughes
[mailto:[EMAIL PROTECTED] I am using Xerces 2.5 and I’m experiencing some
unexpected behaviour, can anyone please tell me if this is expected and if it
is a bug whether or not it has been fixed in a later version. I have a custom InputSource and BinInputStream which I am
using to feed a SAX2XMLReader, I call parseFirst and the parser calls my
BinInputStream::readBytes method. readBytes is asked to read 49152 bytes, I actually read 119
bytes which are the XML fragment in the following lines. <?xml version="1.0"
encoding="iso-8859-1"?> <document><subscribe action=""
constraint="NAB" resource="trade_summary"/> The parser fires the ContentHandler:: startDocument
event, it then calls readBytes on the BinInputStream again without firing the
ContentHandler::startElement event, at this point readBytes blocks waiting for
more input and the program goes no where. This is a problem as am using this mechanism to stream XML
requests to a server via a socket and the client never gets a response. Has anyone seen this? Thanks. |
- unexpected SAX parser behaviour Gary Hughes
- RE: unexpected SAX parser behaviour Gary Hughes
