> Would it be sensible to define an Interface
> similar to XSLT's TraceListener for pure XPath also?
My gut reaction would be no... those are performance intense places and I
would rather not add more feature bloat. But if you can make a really good
case why it makes sense, I might consider.
-scott
"Mikko
Honkala" To: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED] cc: (bcc: Scott Boag/CAM/Lotus)
ut.fi> Subject: RE: Xalan-J: list of referenced
DOM nodes for an XPath
expression?
08/08/2001
08:44 AM
Please respond
to xalan-dev
With a little hacking it seems that I can get the information about which
nodes the XPath expression evaluates on from these 2 methods in
org.apache.xpath.axes.LocPathIterator.java :
public XObject execute(XPathContext xctxt) // for single nodes
public DTMIterator asIterator(
XPathContext xctxt, int contextNode) // for node sets
The problem is that I have to modify Xalan's XPath source in order to send
events from these 2 methods... Would it be sensible to define an Interface
similar to XSLT's TraceListener for pure XPath also?
- Mikko Honkala - http://www.x-smiles.org/
> -----Original Message-----
> From: Gary L Peskin [mailto:[EMAIL PROTECTED]]
> Sent: 7. elokuuta 2001 19:07
> To: [EMAIL PROTECTED]
> Subject: Re: Xalan-J: list of referenced DOM nodes for an XPath
> expression?
>
>
> I'm not sure what you're getting at here, Mikko, but have a look at the
> TraceListener interface. It gets fired whenever a node is selected.
>