Hi Chris, This is the Xerces-J users list. Pretty sure you meant to send this to one of the Xalan mailing lists. Xerces-J doesn't implement this API.
Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] "Chris Schmidt" <[EMAIL PROTECTED]> wrote on 08/15/2007 10:56:15 PM: > Good evening, > > I?m using the CachedXPathAPI.eval(Node, String, PrefixResolver) > method for XPath queries and noticed that the performance wasn?t > better than regular XPathAPI eval calls. In the 2.7.0 version, a > new XPathContext is being created, but in the other eval method the > internal context is used. Is this correct? I don?t see anything on > the user list specifying why the context is being created in one and > not the other. > > The latest version (2.7.1) is slightly different, but still creates > a new context with each call. I modified the code to use the > internal context and there is a definite speed improvement. There > doesn?t seem to be any problems happening at this point, and > threading isn?t a concern at the moment. Is there anything that I > might not be aware of that will cause an issue? > > Thanks, > > Chris Schmidt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
