--On Montag, 10. Dezember 2001 09:16 -0500 [EMAIL PROTECTED] wrote: > This dies out because I proposed an alternative solution (share the > XPathContext in the security code) and was told "Yeah, it looks like that > will work." Unless someone tells me there's still a problem, I'm presuming > this is closed.
I patched both org.apache.xpath.CachedXPathAPI and org.apache.xpath.XPathContext and put these to the xml-security CVS [1]. This implies two problems: 1. If the xml-xalan project adds functionality or bug-fixes the xml-security people don't see these because my patched version "blinds" the xml-xalan version (CLASSPATH order). 2. GUMP is rendered useless [2] for xml-security because the current CVS versions from all libraries are _before_ the xml-security classes. So xml-security does not compile under GUMP. I made the patched in a way that the impact to both classes was as small as possible. But in any way, xml-security needs this patch. Thanks, Christian [1] http://cvs.apache.org/viewcvs.cgi/xml-security/src/org/apache/xpath/ [2] http://jakarta.apache.org/builds/gump/2001-12-10/xml-security.html
