Just my 2 cents but JDOM is inherently slower than other XML
processors and on a mobile platform that's usually not what you want,
you should use SAX or something that's built into the API (if
possible).
I know using SAX and some other methods are a bit more work however if
you're parsing on a
Thanks for the answer. I agree JDOM is slower and uses lot more memory
than a SAX parser, but we already have the implementation in JDOM, and
we wanted to reuse it, at least for the moment. Reuse is allways
faster and in software development you never have enough time. If we
finish the project
Nobody could do it?
I'm going to do some tests changing the input xml, adding aliases for
namespaces and so on. Maybe that exception appears only in some cases
and I can make it work.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post
3 matches
Mail list logo
