<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
No problem, I understand now.<br>
BTW I've decided my desire to replace the XPath factory to work
around a Jaxen bug is in fact a problem with Jaxen instead; it's
just that I have no belief I can get the Jaxen bug fixed ever.<br>
<br>
Since you're re-working the XPath class I'll hold off on any more
uninformed comments...<br>
<br>
Leigh.<br>
<br>
<br>
On 01/20/2012 03:19 PM, Rolf Lear wrote:
<blockquote cite="mid:4F19F685.70703@tuis.net" type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="MS Exchange Server version
6.5.7036.0">
<title>Re: [jdom-interest] suggested JDOM2 improvements</title>
<!-- Converted from text/plain format -->
<p><font size="2">Hi Leigh</font>
</p>
<p><font size="2">I think we are both missing something here.</font>
</p>
<p><font size="2">In JDOM2 I'm convinced that XPath is
deprecated... so, while it is still </font>
<br>
<font size="2">in the ALPHA at the moment it will have a viable
replacement by the next </font>
<br>
<font size="2">ALPHA.</font>
</p>
<p><font size="2">We'll make sure the replacement is 'good' for
custom/other XPath backend </font>
<br>
<font size="2">implementations.</font>
</p>
<p><font size="2">Give me a day to polish up a proposed
replacement. I think you are </font>
<br>
<font size="2">missing the tricks of the XPathFactory code in
the current ALPHA </font>
<br>
<font size="2">release, but there's not much point in fighting
it when it is going to </font>
<br>
<font size="2">change anyway.</font>
</p>
<p><font size="2">Rolf</font>
</p>
</blockquote>
<br>
</body>
</html>