> 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.
BTW if any folks around here want to see Jaxen in action in a JSP tag library setting, the JSTL (JSP standard tag library) EA2 release is out now which features a bunch of XML tags. These are tags for doing XPath and XSLT which are based on the design of the XTags tag library. http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html The current reference implementation of JSTL uses Jaxen as the XPath engine. Right now I think its using the DOM navigator. It'd be nice to make the XML tags in JSTL be model-agnostic so that they can also work with dom4j, EXML and JDOM too. e.g. the JAXM reference implementation is based on dom4j, so it'd be nice to be able to use the XML tags from JSTL to navigate and process JAXM SOAP messages. 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
