Did anyone create an issue in the issue tracker? I think this needs to
be fixed. Unless I missed something, the latest version of the Android
SAX parser supports namespaces. In the absence of a namespace prefix,
a compliant parser should return the same value for qname and
localname. The Android
, September 30, 2008 10:10 AM
To: Android Developers
Subject: [android-developers] Re: SAXParser reports diffeernt qName on SDK
0.9 from SDK 1.0
Hey Brad,
Just to be sure I tested it out and manually typed in amp; into the
source for the web service. I didn't expect this to work, because even
manually
Hey Charlie and Brad,
Good news! I now have the ampersand being parsed correctly. However
the change needed wasn't what we expected. Every time I changed the
raw text in the database from the '' character to the escaped 'amp;'
or '#038;' it didn't work, it would still break at that first
-Original Message-
From: android-developers@googlegroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Cicc
Sent: Tuesday, September 30, 2008 10:10 AM
To: Android Developers
Subject: [android-developers] Re: SAXParser reports diffeernt qName on SDK
0.9 from SDK 1.0
Hey Brad,
Just to be sure
-Original Message-
From: android-developers@googlegroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Cicc
Sent: Monday, September 29, 2008 8:47 PM
To: Android Developers
Subject: [android-developers] Re: SAXParser reports diffeernt qName on SDK
0.9 from SDK 1.0
Hey Brad,
As far as I
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
I have this same issue. I switched to localname as well, but it seems
like as soccercheng notes, you should be able to dictate namespace and
namespace-prefix features. This blows up though, anyone on the team
care to elaborate - should this work with Android, and should a bug be
filed, or what?
Hey Charlie,
I think this should be added to the bug list. I'll do it tonight when
I get home if you haven't already by then...
What I don't understand is this doesn't seem to be an encoding or
namespace issue, since all unicode characters except '' work fine
(that I've tried). As far as I know,
PROTECTED] On Behalf Of Chris Cicc
Sent: Monday, September 29, 2008 4:47 PM
To: Android Developers
Subject: [android-developers] Re: SAXParser reports diffeernt qName on SDK
0.9 from SDK 1.0
Hey Charlie,
I think this should be added to the bug list. I'll do it tonight when
I get home if you haven't
Hey Brad,
As far as I know it doesn't have to be escaped if it's unicode
encoded. In this case, the XML is coming from a .Net Web Service,
which is encoded in UTF-8.
Also, we aren't comparing two different parsers, but rather the old
and new version of the SAXParser with unmodified code.
-chris
@googlegroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Cicc
Sent: Monday, September 29, 2008 8:47 PM
To: Android Developers
Subject: [android-developers] Re: SAXParser reports diffeernt qName on SDK
0.9 from SDK 1.0
Hey Brad,
As far as I know it doesn't have to be escaped if it's unicode
encoded
I ran into the same problem and ended up using the localName since it
appeared to be providing the same information.
I did have to tweak a few things to get it to work, but yea I'm not
sure what changed either.
--~--~-~--~~~---~--~~
You received this message
I need namespce suppoirt also prefix:localname support,
in android, I am not able to set
xr.setFeature(http://xml.org/sax/features/namespaces;, true);
xr.setFeature(http://xml.org/sax/features/namespace-prefixes;,
true);
this will throw exceptions.
I'm using JDOM/Android SAXParser,
JDOM
13 matches
Mail list logo
