Hmmm...
What happens if you feed the results of the 1st expression as the
context of another XPath("item/id") ?
I'm wondering if we aren't treating that item/id steps as an
absolute location-path. We might have a boundary condition on a
step-with-predicate followed by a step, treating the suffix step as an
absolute step.
Anyone on the list have more time than me to track this down?
-bob
On Wed, 7 Nov 2001, MarkW wrote:
> In my previous mail I?d already simplified the xpath expression by leaving
> off the last sub-path.
> Jaxen delivers results using:
> "(/treedata/nodedata)[seekdata/items/item[name='firma' and contains(value,
> 'e')]]"
>
> but not using:
> "(/treedata/nodedata)[seekdata/items/item[name='firma' and contains(value,
> 'e')]]/item/id"
>
> Thanks for any help.
> Mark
>
> > Hmm.. That's probably one of the more complex XPaths I've seen in a while.
> >
> > Can you simplify the path and try to track down which aspect of
> > it isn't working?
> >
> > Ie, does it work without the predicate? Does it work with a
> > simpler predicate?
> >
> > -bob
> >
> > On Wed, 7 Nov 2001, MarkW wrote:
> >
> > > Hi Bob,
> > > tried the following using your demo (with Jaxen 1.0 beta 7 and
> > JDOM beta 7):
> > >
> > > java -classpath
> > >
> > .;e:\lib\jdomb7cvs.jar;e:\lib\saxpath.jar;e:\lib\jaxen10b7.jar;%CLASSPATH%
> > > JDOMDemo treedata.xml
> > "(/treedata/nodedata)[seekdata/items/item[name='firma'
> > > and contains(value, 'e')]]/item/id"
> > >
> > > It returns no result.
> > >
> > > But using this xpath expression it does:
> > > "(/treedata/nodedata)[seekdata/items/item[name='firma' and
> > contains(value,
> > > 'e')]]"
> > >
> > > I get results when I use XPath Tester from FiveSight technologies; so it
> > > can?t be something to do with the xml file or the xpath expression.
> > >
> > > TIA,
> > > Mark
> > >
>
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
