OK, this thread seems to have died off. It looks like xml-security needs the following two patches to get back functional again w/Xalan 2.2. Can I get someone to commit these patches or propose an alternative?
Rationale can be found here: http://marc.theaimsgroup.com/?l=xalan-dev&m=100712430904323&w=2 Index: CachedXPathAPI.java =================================================================== RCS file: /home/cvs/xml-xalan/java/src/org/apache/xpath/CachedXPathAPI.java,v retrieving revision 1.1 diff -u -r1.1 CachedXPathAPI.java --- CachedXPathAPI.java 2001/11/29 16:30:47 1.1 +++ CachedXPathAPI.java 2001/12/08 18:21:03 @@ -105,6 +105,10 @@ */ XPathContext xpathSupport = new XPathContext(); + public XPathContext getXPathContext() { + return this.xpathSupport; + } + /** * Use an XPath string to select a single node. XPath namespace * prefixes are resolved from the context node, which may not Index: XPathContext.java =================================================================== RCS file: /home/cvs/xml-xalan/java/src/org/apache/xpath/XPathContext.java,v retrieving revision 1.30 diff -u -r1.30 XPathContext.java --- XPathContext.java 2001/08/20 23:47:11 1.30 +++ XPathContext.java 2001/12/08 18:21:03 @@ -139,6 +139,10 @@ return m_dtmManager; } + public void setDTMManager(DTMManager dtmManager) { + this.m_dtmManager = dtmManager; + } + /** * Get an instance of a DTM, loaded with the content from the * specified source. If the unique flag is true, a new instance will - Sam Ruby
