Hi once again,

The patch has been updated, since the original had a problem with the parent
axis. The current patch now passes all the existing Jaxen test cases, and is
factored a wee bit better for clarity.

The patch is in the Jaxen patch manager at:

http://sourceforge.net/tracker/?atid=402188&group_id=31447&func=browse

Cheers,

Nicholas.
mailto:[EMAIL PROTECTED]

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 07, 2001 2:38 PM
Subject: [Jaxen] [Patch] Entity reference support for DOM Navigator


>
> Hi all,
>
> Please find in the Jaxen patch manager a patch that allows the
> org.jaxen.dom.DocumentNavigator class to handle entity references.
>
> Entity references are tricky to deal with using the W3C DOM model, since
> they involve a degress of traversing up and down when looking for nodes
> that the XPath specification sees as being at the same depth in the tree.
>
> As a consequence the code is not as clean as the original DOM
> implementation. In fact, you'll see a fair degree of redundancy in
> getChildAxisIterator and getFollowingSiblingAxisIterator. You'll see that
> getPrecedingAxisIterator follows a very similar pattern as well.
>
> I've done some basic testing of the code against DOM 1 (though I see no
> reason why DOM 2 wouldn't work just as well). I guess you'll be after some
> test cases at some point as well ;).
>
> The code is patched against the 1.0-beta-7 release, though a quick look at
> CVS doesn't show any more recent changes to the DocumentNavigator.
>
> I'm subscribed to the mailing list, so if you have any questions, I'll be
> listening here.
>
> Cheers,
>
> Nicholas Cull
> [EMAIL PROTECTED]



_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest

Reply via email to