Comments on: The Force Unleashed: XML+XPath on Android using dom4j and Jaxen http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/ Tech And Talk - by Matthias Käppler Thu, 17 Dec 2009 09:41:00 +0000 http://wordpress.com/ hourly 1 By: anoymous http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-679 anoymous Mon, 30 Nov 2009 23:07:57 +0000 http://brainflush.wordpress.com/?p=83#comment-679 The benchmark is applicable for any devices and processor types, a comparison with SAX type is somewhat difficult because, SAX is very low level and doesn't support random access, yet VTD outperforms SAX by a typical 2 times, and still support XPath,random acess and has its signature of ease of use... The benchmark is applicable for any devices and processor types, a comparison with SAX type is somewhat difficult because, SAX is very low level and doesn’t support random access, yet VTD outperforms SAX by a typical 2 times, and still support XPath,random acess and has its signature of ease of use…

]]> By: Matthias Käppler http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-672 Matthias Käppler Wed, 25 Nov 2009 08:49:14 +0000 http://brainflush.wordpress.com/?p=83#comment-672 That's a rather interesting concept. Do you have benchmarks for mobile devices, in particular, Android? Also, I was really missing a comparison to a pure SAX parser. What are the dependencies of the Java implementation? That’s a rather interesting concept. Do you have benchmarks for mobile devices, in particular, Android? Also, I was really missing a comparison to a pure SAX parser. What are the dependencies of the Java implementation?

]]> By: Anonymous http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-671 Anonymous Wed, 25 Nov 2009 08:36:31 +0000 http://brainflush.wordpress.com/?p=83#comment-671 vtd-xml has the industry leading parsing and xpath performance <a href="http://vtd-xml.sf.net" rel="nofollow">vtd-xml</a> vtd-xml has the industry leading parsing and xpath performance

vtd-xml

]]> By: Matthias Käppler http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-656 Matthias Käppler Fri, 13 Nov 2009 09:57:10 +0000 http://brainflush.wordpress.com/?p=83#comment-656 sources are now on my GitHub account: http://github.com/kaeppler/dom4j-1.6.1-harmony sources are now on my GitHub account:
http://github.com/kaeppler/dom4j-1.6.1-harmony

]]> By: Jan Berkel http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-649 Jan Berkel Tue, 20 Oct 2009 13:01:59 +0000 http://brainflush.wordpress.com/?p=83#comment-649 just found another option: there's a sax driver for android's pull parser, which you can use like so: <code> XmlPullParser parser = org.xmlpull.v1.XmlPullParserFactory.newInstance().newPullParser(); Driver driver = new org.xmlpull.v1.sax2.Driver(parser); driver.parse(new InputSource(...)); </code> just found another option: there’s a sax driver for android’s pull parser, which you can use like so:


XmlPullParser parser = org.xmlpull.v1.XmlPullParserFactory.newInstance().newPullParser();
Driver driver = new org.xmlpull.v1.sax2.Driver(parser);
driver.parse(new InputSource(...));

]]> By: Matthias Käppler http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-648 Matthias Käppler Tue, 20 Oct 2009 07:49:56 +0000 http://brainflush.wordpress.com/?p=83#comment-648 Hi Jan, yes, good point. In fact, I've recently switched to git for version control on all projects I work on, and I plan to move some of them to GitHub anyway. I'll let you know once that's done so everyone can hack away on those dom4j sources more easily. Hi Jan,

yes, good point. In fact, I’ve recently switched to git for version control on all projects I work on, and I plan to move some of them to GitHub anyway. I’ll let you know once that’s done so everyone can hack away on those dom4j sources more easily.

]]> By: Jan Berkel http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-647 Jan Berkel Mon, 19 Oct 2009 22:57:50 +0000 http://brainflush.wordpress.com/?p=83#comment-647 hi matthias, thanks for your work on this, i've been trying to get xml working on android for quite a while now. how about svn importing dom4j into github and then have a separate branch containing your harmony fixes? i'd be happy to set it up if you send me the diff. hi matthias,

thanks for your work on this, i’ve been trying to get xml working on android for quite a while now. how about svn importing dom4j into github and then have a separate branch containing your harmony fixes? i’d be happy to set it up if you send me the diff.

]]> By: Matthias Käppler http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-645 Matthias Käppler Tue, 29 Sep 2009 15:10:38 +0000 http://brainflush.wordpress.com/?p=83#comment-645 Hey Eric, I also have a small XML parser abstraction for Android in the pipe (I plan to release this as part of my DroidFu utility library for Android) which is purely based on the XML Pull Parser implementation shipped with Android. Nothing special really, but it takes care of wrapping boilerplate code (such as skipping whitespace between nodes and normalizing whitespace in text nodes) and works with minimal configuration effort, so you can focus on the actual task. It uses reflection to allow being used like this: <code> class MyModelParser extends XmlModelParser { // currentItem is a MyModel public void onFooTag(String content, Map attributes, String parentNode) { this.currentItem.setFoo(new Foo()); } public void onFooText(String text) { this.currentItem.getFoo().setValue(text); } ... } parser = new MyModelParser(); List results = parser.parse(someInputStream); </code> when instantiated, the parser will take note of which callback methods are defined, and invoke them automatically when a matching tag or text node is spotted in the stream. it's a simple thing, but works well enough for small documents. still have to test whether or not it's affected by the unicode expansion problem. Hey Eric,

I also have a small XML parser abstraction for Android in the pipe (I plan to release this as part of my DroidFu utility library for Android) which is purely based on the XML Pull Parser implementation shipped with Android. Nothing special really, but it takes care of wrapping boilerplate code (such as skipping whitespace between nodes and normalizing whitespace in text nodes) and works with minimal configuration effort, so you can focus on the actual task.

It uses reflection to allow being used like this:


class MyModelParser extends XmlModelParser {

// currentItem is a MyModel

public void onFooTag(String content, Map attributes, String parentNode) {
this.currentItem.setFoo(new Foo());
}

public void onFooText(String text) {
this.currentItem.getFoo().setValue(text);
}
...
}

parser = new MyModelParser();
List results = parser.parse(someInputStream);

when instantiated, the parser will take note of which callback methods are defined, and invoke them automatically when a matching tag or text node is spotted in the stream.

it’s a simple thing, but works well enough for small documents. still have to test whether or not it’s affected by the unicode expansion problem.

]]> By: Eric Mill http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-644 Eric Mill Tue, 29 Sep 2009 14:36:36 +0000 http://brainflush.wordpress.com/?p=83#comment-644 Thanks for posting this. As you can tell by the continued comments, a good, simple XML parser in Android is still definitely a community need. Thanks for posting this. As you can tell by the continued comments, a good, simple XML parser in Android is still definitely a community need.

]]> By: Matthias Käppler http://brainflush.wordpress.com/2009/05/19/the-force-unleashed-xmlxpath-on-android-using-dom4j-and-jaxen/#comment-643 Matthias Käppler Tue, 22 Sep 2009 16:51:49 +0000 http://brainflush.wordpress.com/?p=83#comment-643 You're right, it's indeed the BSD license. What got me turned off was this: <blockquote> 3. The name "DOM4J" must not be used to endorse or promote products derived from this Software without prior written permission of MetaStuff, Ltd. For written permission, please contact dom4j-info@metastuff.com. 4. Products derived from this Software may not be called "DOM4J" nor may "DOM4J" appear in their names without prior written permission of MetaStuff, Ltd. DOM4J is a registered trademark of MetaStuff, Ltd. </blockquote> That doesn't sound very liberal after all, since I couldn't give a derived project a name like dom4j-android. Any name not containing dom4j would completely obscure my intention: fix dom4j to run on Harmony. You’re right, it’s indeed the BSD license. What got me turned off was this:

3. The name “DOM4J” must not be used to endorse or promote
products derived from this Software without prior written
permission of MetaStuff, Ltd. For written permission,
please contact dom4j-info@metastuff.com.

4. Products derived from this Software may not be called “DOM4J”
nor may “DOM4J” appear in their names without prior written
permission of MetaStuff, Ltd. DOM4J is a registered
trademark of MetaStuff, Ltd.

That doesn’t sound very liberal after all, since I couldn’t give a derived project a name like dom4j-android. Any name not containing dom4j would completely obscure my intention: fix dom4j to run on Harmony.

]]>