Oops you're quite right. I am using Xalan strictly as an API to evaluate XPath expressions. I'm not using XSL at all. In fact I am using Xerces as my DOM parser so all of my interactions with Xalan have to go through the wrapper. Right now I'm using the class xalanc::XPathEvaluator to get back an XObject. However, now I need to go a step further and analyze all of the dependent nodes in doing the XPath expressions. Any suggestions would be appreciated. It seems like right now I'll end up having to reimplement the XPath::execute functionality and build my own intermediate node list.
Steve ----- Original Message ----- > Not a lot of information in your request (at least from my perspective > of a fairly recent XSL developer). What's the context? Are you using > XSL? In XSL you could do the following: > > <xsl:variable name="fooNodeSet" select="/foo" /> > > At that point, you would have an XSL variable represeting the set of > /foo nodes (and all descendents) which you could then process. > > You might want to repost with a little more information about what > domain/context your working in and what your goals are? > > Ed > > > > Steve Breitenbach wrote: > > > > Does anyone have any suggestions for how to go about > > the task of finding a node set from an XPath, where the > > node set contains all nodes that the XPath expression > > depends on, regardless of return type? For example, > > if the expression was "count(/foo)", how does one go > > about getting the set of nodes return by location path > > "/foo"? Any suggestions would be appreciated. > >
