[android-developers] What's on earth the SAX Parser changes between 2.1 and 2.2
I have wrote a ContentHandler for SAX parser to retrieve data from and xml file, but it does't work on 2.1-update1, but works fine on 2.2, What is on earth is the changes, anyone knows? the problem I encountered is exactly the same as stated at: http://code.google.com/p/android/issues/detail?id=11223 *Reported by m.de.kwant, Sep 14, 2010* My application uses a urlconnection to retrieve a soap response. This XML is run through the default saxparser available in the java/android lib. In android version 2.1 the XML is not parsed correctly. I fact there seems to be no parsing at all, while the raw input is available. In android version 2.2 the input XML is parsed and the return result from my handlers is correct. In short. SaxParser on 2.1 does nothing (no result, no error, no parsing), Saxparser on 2.2 works like it supposed to work. Are there any work arounds for this problem ? *Comment 1 by project member e...@google.com, Sep 14, 2010* you can have a look at the differences between 2.1 and 2.2 yourself. Status: Declined Owner: e...@google.com Labels: Component-Dalvik Delete comment Comment 2 by jiangjun.jking, Today (95 minutes ago) I have the same issue, could you please explain more clear about it? -- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] What's on earth the SAX Parser changes between 2.1 and 2.2
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 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 android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: What's on earth the SAX Parser changes between 2.1 and 2.2
Ok, I wrote it in english, hoping it can be read by more people who have the same issues, if some one has the problem, they will read it carefully regardless the poor syntax. Apparently, you are not. My test code is aimed to work on both 2.1 and 2.2, which have different implementation of SAX, 1.6, even 1.5 have delivered with large amount of handset, that should not be ignored. :) On Mon, Oct 11, 2010 at 12:23 AM, Indicator Veritatis wrote: > 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 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 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 > android-developers@googlegroups.com > > > To unsubscribe from this group, send email to > > > android-developers+unsubscr...@googlegroups.com > > > > > > 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 android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
