commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32360] - [jxpath] Default Namespace not handled correctly
Date Thu, 03 Nov 2005 22:38:06 GMT
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





------- Additional Comments From dmitri@plotnix.com  2005-11-03 23:38 -------
1. The GUMP failure had little to do with this bug.  They had to do with the 
version of JDOM.  I have already made a change to bring JXPath in line with 
JDOM 1.0 (it was on b9 before), so the GUMP complaints will hopefully stop.

2. We have switched from the CVS repository to SVN.

3. XPath 2.0 or not: that's a timely question.  They released a candidate 
recommendation for XPath 2.0 today (Nov 3, 2005). Yay!!! 

See http://www.w3.org/TR/xpath20/ 

Hopefully the final document will not differ from this recommendation in any 
significant way. Should we start looking into implementing it? Will somebody be 
willing to help? I personally don't have the cycles this undertaking would 
require.

Philosophically speaking, does JXPath really need to follow the latest 
standards?  After all, its original purpose was to apply XPath syntax to 
JavaBeans. With JavaBeans, all intricacies of namespaces and axes and 
predicates and document order etc are irrelevant or unimportant. Now and then I 
discover some problems with JXPath's implementation of more esoteric parts of 
the spec, but I never get any bug reports around those issues.  To me this 
means that people do not use JXPath's implementation of XPath to the full 
extent.  Perhaps most users basically stick to paths like "/a/b/c" or "//foo
[bar=3]".  XPath 1.0 is perfectly sufficient for those. 

To re-phrase the question: what role do we want JXPath to play in the general 
Apache platform?  Should it be on par with Xalan and other implementers of W3C 
Standards or should it remain what it is today: a kitchen utensil for those who 
like mixing oil and water (i.e. XPath and JavaBeans)?

-- 
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


Mime
View raw message