You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by __matthewHawthorne <ma...@phreaker.net> on 2004/01/21 07:09:31 UTC

Jxpath vs. Jaxen?

I'm frequently finding myself needing a "Bean query language", and then 
I remembered that Jxpath can do this easily.

But I've done a little reading about Jaxen and wondering if I should 
give this library it's day in court also.

I'm continuing the investigation, but I'm interested in what others have 
to say.  Anyone have feelings favoring one or the other?

Apache vs. Codehaus -- who will triumph?  It's a true battle of the titans.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: Jxpath vs. Jaxen?

Posted by Dmitri Plotnikov <dm...@apache.org>.
Matthew,

If you have the need to traverse through Java Beans, Maps, Collections etc,
JXPath does all of that out of the box. Plus it supports mixed models, e.g.
a map containing DOM documents or a Java Bean that has a JDOM document as
the value of some property.

Jaxen is better suited for homogenous representations of XML, such as DOM,
JDOM, DOM4J etc. It supports a much wider varieties of in-memory
representations of XML than JXPath.  You can make Jaxen traverse non-XML
object graphs, but you would have to provide your own implementations of
some Jaxen APIs.

So, to summarize: with pure XML, try either Jaxen or JXPath (or for that
matter Xalan if you are working with DOM). With non-XML objects in the
picture - go with JXPath.

- Dmitri

----- Original Message ----- 
From: "__matthewHawthorne" <ma...@phreaker.net>
To: "Jakarta Commons Developers List" <co...@jakarta.apache.org>
Sent: Wednesday, January 21, 2004 1:09 AM
Subject: Jxpath vs. Jaxen?


> I'm frequently finding myself needing a "Bean query language", and then
> I remembered that Jxpath can do this easily.
>
> But I've done a little reading about Jaxen and wondering if I should
> give this library it's day in court also.
>
> I'm continuing the investigation, but I'm interested in what others have
> to say.  Anyone have feelings favoring one or the other?
>
> Apache vs. Codehaus -- who will triumph?  It's a true battle of the
titans.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: Jxpath vs. Jaxen?

Posted by Stephen Colebourne <sc...@btopenworld.com>.
From: "__matthewHawthorne" <ma...@phreaker.net>
> I'm frequently finding myself needing a "Bean query language", and then
> I remembered that Jxpath can do this easily.
I have only used Jaxen, and found it easy to work with, however I had to add
my own code for navigating JavaBeans.

Stephen


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org