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" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
