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] - Default Namespace not handled correctly
Date Thu, 06 Jan 2005 23:55:11 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


runger@cim.mcgill.ca changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement




------- Additional Comments From runger@cim.mcgill.ca  2005-01-07 00:55 -------
Sorry to annoy you about this again, but I have been thinking about it, and
decided that I feel strongly enough about it to give it another try...

While I cannot argue the point about what the XPath specifications say, I feel
this is not enough reason to discard out of hand setting a no-prefix namespace
for JXPathContexts.

After all, both XSLT 1 and 2 behave in the way I describe (at least xalan and
saxon do) - you can set a no prefix namespace in the XSL document and the xpath
expressions in the XSL will be correctly evaluated against XML elements of this
namespace.

Not permitting this feature limits JXPaths usefulness, particularily when
attempting to process XML documents in an automated way, where the XPath
expressions do not come directly from handwritten code, but rather are extracted
from some other document, or input by the user.

Finally, I must admit that while I did not consult the XPath spec in advance
before submitting the bug, intuitively most programmers would expect it to work
with no-prefix namespaces, the same way as XPath in XSLT.

I beg you to reconsider your decision, esp. since I believe it would be a very
simple change in the code - just permit NULL or the empty string to be
registered as a prefix, and interpret this as the no-prefix namespace.


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