I switch to use http://twitter.com/statuses/public_timeline.xml, and jdom does not throw the same error.
I check xml specs and here is what I think: the data mining feed "http://twitter.com/statuses/ public_timeline_partners_#####.xml returns xml document containing an invisible "end of medium" (maybe end of line, see http://www.fileformat.info/info/unicode/char/0019/index.htm) at line 8148. this character has unicode 0x19, which is not a recommended char (see http://www.w3.org/TR/REC-xml/#charsets). jdom parser complains about this invalid char. I think you can reproduce the problem by using any data mining feed (xml format) and test it with jdom parser (code in my first email). To solve the problem, please make sure no invalid xml char like "end of medium" character is inserted into the xml when the xml feed is created. this error occurs often before, but today every data mining xml feed has the invalid char. thanks for helping, -aj On May 6, 7:21 pm, Cameron Kaiser <spec...@floodgap.com> wrote: > > I'm getting this xml parsing error all day long. I'm using jdom.jar > > and pass twitter api xml response directly to build jdom document. > > Looking at the xml file right now, but hope you can take at look at it > > as well. I expect other jdom users may see the same error. > > > 2009-05-06 19:11:49,401 ERROR feed.XmlFetcher (XmlFetcher.java:run > > (136)) - failed to fetchhttp://twitter.com/statuses/public_timeline.xml; > > org.jdom.input.JDOMParseException: Error on line 8148: An invalid XML > > character (Unicode: 0x19) was found in the element content of the > > document. > > The problem is that the view moves so fast that it's unlikely it's still > there. When you dump the raw data, what is the last status ID you see before > it bugs out? > > -- > ------------------------------------ personal:http://www.cameronkaiser.com/-- > Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com > -- It's the car, right? Chicks dig the car. -- "Batman Forever" > ---------------
