I am having a similar problem. It looks like the startElement and endElement methods of our ContentHandler are never called.
I'm guessing this is related to the Xml Pull Parser changes introduced in 1.0rc1 On Sep 29, 7:08 am, Chris Cicc <[EMAIL PROTECTED]> wrote: > Hello, > I am also having a problem with the SAXParser that I believe is > similar to your problem. I had a parser for a basic XML document that > contained only nodes and text. This was working find for weeks with > 0.9. But after the change to 1.0 RC1 it no longer works properly. > > Now, when it hits a node that contains the text, for instance "test & > text", it will separate it into three records, "test", "&", "text". > With 0.9 this would return "test & text" as you would assume. Using > other special characters, such as % and *, work as expected. Anyone > else see behavior like this? > > Any suggestions? > > Thanks, > Chris > > On Sep 24, 11:09 am, Stefan Handschuh <[EMAIL PROTECTED]> wrote: > > > Following scenario: > > > SAXParsersaxParser= saxParserFactory.newSAXParser(); > > > XMLReaderxmlReader=saxParser.getXMLReader(); > > > xmlReader.setContentHandler(handler); > > xmlReader.parse(someImputStream); > > > where handler implements ContentHandler. > > >xmlReader.parse(..) calls handler.characters(..) but neither > > handler.startElement(..) nor handler.endElement(..). > > > This worked well in 0.9. > > > Can this regression be reproduced by anybody? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
