Its actually because EXML doesn't properly support whitespace handling - Jaxen is behaving properly.
I've taken the EXML test target (test.exml) out of the 'test' build target so we won't confuse ourselves over this one again. If your test target got this far then Jaxen is passing all the unit tests. James ----- Original Message ----- From: "Eddie McGreal" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 26, 2002 1:26 PM Subject: [Jaxen] JUnit test fails > Hi, > > the current build cause one test to fail. I'm not sure whether the failed > test is significant but I guess none of the test should fail > Here is the output : > > [junit] Document [xml/pi2.xml] > [junit] Initial Context :: /a/c > [junit] Select :: //processing-instruction() > [junit] Expected Size :: 1 > [junit] Result Size :: 1 > [junit] Select :: preceding-sibling::* > [junit] Expected Size :: 1 > [junit] Result Size :: 1 > [junit] Select :: preceding-sibling::node() > [junit] Expected Size :: 5 > [junit] Result Size :: 2 > [junit] ## FAILED > [junit] ## xpath: preceding-sibling::node() = [(DefaultXPath): > [(DefaultRelativeLocationPath): [(DefaultAllNodeStep): preceding-sibling]]] > [junit] --> <?toc order-by="x"?> > [junit] --> <b>foo</b> > > Regards > Eddie > > _______________________________________________ > Jaxen-interest mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jaxen-interest _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
