> > > If you execute "/foo/bar/baz[1]" on this document, Jaxen returns a list
> > > of size 1, presumably containing the very first "baz". The correct
> > > behavior should be to return a list containing the first baz in the
> > > first bar and the first baz in the second bar, i.e. a list of size 2.
> > Right.
>
> .. and btw this is a major show-stopper. Although I don't want to sound
> patronising, I wouldn't suggest you guys release 1.0 before fixing this
> one :)
Oh, I agree. No worries there.
> > Would you like to try hunting down this exact bug?
> > Hopefully this URL will work. If not, just look at DefaultLocationPath:
>
> I'll give it a try.
>
> > If you can't track down the bug, could you at least create a test-case
> > for our test-harness, so we can replicate it in a controlled environment?
>
> I've got a program that creates the bug, so I can put that in your test
> framework. I haven't got junit installed at the moment though, so I
> don't know if I'll have the time to make it all work.
junit.jar should be included in the lib/ directory of the distribution.
Check out the xml/test/tests.xml file, which is our test driver file.
Add your test there, and possibly toss in another test document into
the xml/tests/ directory, if none of the current ones are sufficient
for exposing the bug.
Then, from a command-line:
./build.pl test.all
(or test.dom4j, or test.<your-object-model>).
Which object-model are you using, by the way?
If you can track this down, and have a fix, I'll grant you CVS
write access to integrate your changes back, if you like. Just
send me your sourceforge username.
-bob
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
