From: "Samuel Cheung" <[EMAIL PROTECTED]> > Hi, > > Could some one please tell me the differences between Jaxen Vs JxPath in > Jakarta Common project?
JXPath started by a guy called Dmitri who we tried to bring to the Jaxen party but he wanted to go on his own. JXPath started with JavaBeans as its focus, an XPath engine for beans. Its still pretty much just Dmitri working on JXPath and I've no idea how close to XPath 1.0 that JXPath has got, given its bean bias. Jaxen grew out of the dom4j and JDOM communities as being a fully XPath 1.0 engine that could work on any representation of the XML InfoSet. Quickly W3C DOM and Electric XML were added - so all the common XML models are now supported. Jaxen will add support for java beans too one day. My other totally biased oppinions are that Jaxen has a lot more developers behind it (9 at last count) as well as a much larger user community: the whole of the dom4j and JDOM communities pretty much use Jaxen as their XPath engine, some of the DOM communities (such as Reuters NewsML toolkit) use Jaxen too. So I've more confidence that Jaxen supports XPath 1.0 than JXPath. Plus Jaxen is used in the JSTL / Web Services Pack reference implementation from Sun as its XPath engine. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
