As I understand from the javadoc, an XPath object can be viewed as a 'precompiled' xpath expression, that can be used for successive evaluations, which will increase performance. However, in my case, the same XPath object will be used by lots of concurrent threads (I assume this is possible), where each thread has its own variables. However, in Jaxen, a specific VariableContext is tied to an XPath instance!
This is a problem for me, because I have to create a new XPath instance each time, which I think will be costly because of expression parsing. It seems an unnecessary restriction of Jaxen, or am I missing something here? Ruud Diterwich ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
