Saxon

Legacy ID: #5154842 Legacy Poster: Ryan Gustafson (rgustav)

I'm working on integrating Saxon-B as the XPath 2.0 engine for PMD. I'm using the net.sf.saxon.sxpath.* packages so things run on 1.4 without JAXP, and the net.sf.saxon.om.* package to adapt the PMD AST in hopes of getting the best performance possible. While trying to expose Rule properties as variables, I'm getting the same error "Supplied XPathVariable is bound to the wrong slot: perhaps it was created using a different static context", as describe in this thread about a month ago: http://sourceforge.net/mailarchive/forum.php?thread_name=486DF502.3000506%40uva.nl&forum_name=saxon-help I debugged a bit, and the problem seemed to be caused by an ordering problem when taking XPathVariables from a Map, and placing them into a List, and still assuming the 'slotNumber' on the XPathVariable works in the List. Supposedly there's a fix for this in SVN. I'm not having any luck building SVN using 'build.xml bj', as it seems to want some code from Saxon-SA available? Is there documentation available on doing builds from SVN? Or, is there a regular snapshot of SVN available somewhere that I can test out to see if the problem is corrected? Another question on setting variable values... the only way I've figured out how to do this so far is to define the XPathVariables using the XPathStaticContext from the XPathEvaluator, saving the XPathVariables off, and then getting an XPathExpression, creating a XPathDynamicContext, and calling setVariable(XPathVariable,ValueRepresentation) using the XPathVariable references from earlier. Is there a more direct way to set variable values? If not, is there an easier route to get the XPathVariable references when I'm working with the XPathDynamicContext, that doesn't require me to manual remember them when I define them? I'm really just looking for something like XXXContext.setVariable(String variableName, Object value), but it doesn't appear to be that straightforward with these APIs. (The javax.xml.xpath APIs are much easier, but that requires JAXP, and performance using DOM was 3 times works than Jaxen). Thanks, Ryan