So if I read your blog post correctly, the problem is not a new bug introduced in 2.2, it is that your test code only worked because of a bug present in 2.1, but fixed in 2.2.
But I have to admit I didn't spend that much time studying the blog post. I might have if I did not find the misuse of English verb tenses so off-putting. Also, your blog will show up better in searches if you fix the spelling of 'exception': you wrote 'excpetion'. On Oct 9, 7:42 am, Jun Jiang <[email protected]> wrote: > Thanks, frank, I have found the cause of my problem, you can refer my blog > post for more detail: > > http://mmmyddd.freeshell.net/blog/Computer/Android/saxcompatibility > > On Thu, Oct 7, 2010 at 11:58 PM, Frank Weiss <[email protected]> wrote: > > The bug report sheds no more light on the problem than you did. I've used > > the same SAX parser code on 2.1 as on 2.2 without issues. I suspect there's > > either an issue in your default handler code or in the XML being read. > > > Have you tried to step through the code on 2.1-update1? Did you implement > > the characters callback correctly? Did you look at the changes in the > > library code, as the bug report suggested? > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected]<android-developers%[email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] 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
