Sam Ruby (and perhaps others) have noticed that some of the internal APIs associated with Xalan's XPath code have changed. I think this is due to some security fixes (see http://issues.apache.org/jira/browse/XALANJ-2008 ). The patch in XALANJ-2008 has a number of XPath changes.
I don't think that Xalan can make adjustments here on its internal APIs which were changed for reasons of plugging security holes. That said, the public APIs: http://xml.apache.org/xalan-j/apidocs/org/apache/xpath/CachedXPathAPI.html http://xml.apache.org/xalan-j/apidocs/org/apache/xpath/XPathAPI.html are going to continue to be supported. For now Apache Xalan can not support the XPath APIs that are part of JAXP 1.3 because the JAXP 1.3 implementation belongs to Sun and Apache can't have a dependancy on Sun's code. That doesn't stop an individual from getting the code from Sun (as pointed out by Santiago Pericas-Geertsen). - Brian - - - - - - - - - - - - - - - - - - - - Brian Minchau XSLT Development, IBM Toronto e-mail: [EMAIL PROTECTED] "You want it today? Sorry, I thought tomorrow would be yesterday and I still had more time." - My daughter Jennifer
