Actually I was thinking that the contents of an Expression object could be
publicly read ( Expression#getChildExpressions() ). This way an interested
application could traverse the expression tree and check the LocPath
expressions itself.
- Mikko Honkala - http://www.x-smiles.org/
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 10. elokuuta 2001 22:19
> To: [EMAIL PROTECTED]
> Subject: RE: Xalan-J: list of referenced DOM nodes for an XPath
> expression?
>
>
>
> "Mikko Honkala" <[EMAIL PROTECTED]> wrote:
> > Maybe a better performing approch of getting this information
> would be to
> > add interface to the org.apache.xpath.Expression, which would allow
> reading
> > the expression tree after compilation. That way the actual XPath
> execution
> > would remain untouched. Does this sound more doable?
>
> You're saying this would be done as sort of a special itteration?
> i.e. put
> in a XPath#getDependencies(...) method or some such, which would do a
> special walk and return the dependencies? Hmm... sounds like a lot of
> work.
>
> -scott
>
>
>
>
>
