Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
From: bugzilla@apache.org
To: commons-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 32360]  -
    [jxpath] Default Namespace not handled correctly
Message-Id: <20051101090815.0FDA0599@ajax.apache.org>
Date: Tue,  1 Nov 2005 10:08:15 +0100 (CET)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32360>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32360


elharo@metalab.unc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |


------- Additional Comments From elharo@metalab.unc.edu  2005-11-01 10:08 -------
JXPath does not claim to and does not implement XPath 2.0. It implements XPath
1.0. XPath 2.0 is a very different spec with many things to recommend it and a
few things not to like as well. However XPath 2 is not compatible with XPath 1.
Regardless of how much one likes or dislikes XPath 2, it is essential that
JXPath be clear about which version it supports. If the goal is to support XPath
1, then this is still a bug. If the goal is to support XPath 2, then that should
be stated up front, and then about 2000 more bugs need to be filed to cover the
parts of XPath 2 that JXPath does not handle. 

Currently, the JXPath web site states, "The official definition of XPath by W3C
can be found at XML Path Language (XPath) Version 1.0." I think that's pretty
clear. JXPath supports XPath 1.0. The code base also makes that obvious, though
perhaps the web site could be rewritten to make this a little more obvious.
(Most of the site was probably written when XPath 2.0 was a little further
away.) The current release plan should focus on XPath 1.0 compatibility. 

It might indeed be laudable in the future to make a branch of JXPath that
supports XPath 2. We could probably call it JXPath 2. Nice and symmetrical.
However that's a huge undertaking that will likely take years, not something we
can do with one method overnight. It might require a complete rethink of the
entire architecture of JXPath. The data model in XPath 2.0 is really that
different. But for the time being, all references to the spec shoudl be to the
one JXPath actually implements, which is XPath 1.0. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org