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 The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and destroy all copies of the original message. Thank you
