From: "bob mcwhirter" <[EMAIL PROTECTED]> > > Another thought; how about a generic XPath implementation. Say > > > > org.jaxen.generic.XPath > > > > Which depending on the type of the context it could deduce if it was DOM, > > dom4j, EXML or JDOM and call the necessary exact XPath implementation? > > Hopefully it could share the XPath expression though. > > Yah, XPath expressions are shareable, no problem. You just need some > logic to determine which Navigator to pass to the forms of > selectNodes(...) et al that take a Navigator.
Yep - I was thinking we could have a 'generic' XPath implementation that looked at the type of the 'node' to determine if its DOM, dom4j, EXML, JDOM etc. So it would switch navigators based on the type of the incoming node. Then if, say, the JSP standard tag library (JSTL) were to use the 'generic' XPath implementation it would silently work with all of Jaxen's supported models, without the JSTL guys needing to do any work. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
