Hi All,
I have a socket receiving streams of XML. I receive an InputStream,
but short of a dirty hack, do not know when (or how) I pass the
stream/contents to be parsed. Any thoughts/resources on parsing streaming
XML please?
Thanks
Paul.
See XmlPull:
http://www.xmlpull.org/
On 8/15/05, Paul Wallace [EMAIL PROTECTED] wrote:
Hi All,
I have a socket receiving streams of XML. I receive an InputStream,
but short of a dirty hack, do not know when (or how) I pass the
stream/contents to be parsed. Any thoughts/resources on
Hi,
the problem is not only a delay but also an order of the messages. I
think all messages should be flushed to the file as soon as they come.
When I choosing to log 'info' messages I accept the fact that it will
slow down the processing of requests. That is always a drawback of
logging. The
You can use different things, but directly programming
you can use SAX2, XMLReader, and
XMLReaderFactory.createXMLReadersee JDK javax.xml
package documentation. You could use a DOM object,
but I wouldn't recommend it because of memory usage.
You can change the underlying XML parser impls for
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36169.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Did tomcat move to svn already ?
Costin
[EMAIL PROTECTED] wrote:
Author: markt
Date: Sun Aug 14 04:48:32 2005
New Revision: 232601
URL: http://svn.apache.org/viewcvs?rev=232601view=rev
Log:
Remove CVS closure warning from SVN
Removed:
tomcat/watchdog/branches/tc4.1.x/WARNING.txt
Watchdog has moved but the rest remains with CVS. We have until the
end of the year to migrate the rest.
Mark
Costin Manolache wrote:
Did tomcat move to svn already ?
Costin
[EMAIL PROTECTED] wrote:
Author: markt
Date: Sun Aug 14 04:48:32 2005
New Revision: 232601
URL:
Bill Barker wrote:
As a historical note, this really should be the tc3.2.x branch. This
particular watchdog has never worked well with any TC 3.3.x, since it
has a lot of bugs related to specific implementation details of TC 3.2.x
(and, the Watchdog committers mostly moved on to TC 4.0.x
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31125.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=31125.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Mark Thomas wrote:
Bill Barker wrote:
As a historical note, this really should be the tc3.2.x branch. This
particular watchdog has never worked well with any TC 3.3.x, since it
has a lot of bugs related to specific implementation details of TC
3.2.x (and, the Watchdog committers mostly
- Original Message -
From: Mark Thomas [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Monday, August 15, 2005 11:00 AM
Subject: Re: svn commit: r232600 -
/tomcat/watchdog/branches/tc3.3.x/WARNING.txt
Mark Thomas wrote:
Bill Barker wrote:
As a
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36198.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36198.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36199.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi thanks,
Parsing a file would not normally be a problem, but as it is a
stream, there is no EOF and when I parse the stream into:
DocumentBuilder db =
DocumentBuilderFactory.newInstance().newDocumentBuilder();
db.parse(in);
I get:
org.xml.sax.SAXParseException: The processing
16 matches
Mail list logo