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 Wed, 02 Nov 2005 04:56:57 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-02 05:56 -------
Who would've thought that this issue would turn into such a bloodshed. We now 
have two diametrically opposite sides. Of course, we'll make a decision at some 
point and one of the two sides will lose. :(  That's unless somebody can come 
up with an idea for a peacefull resolution.  

Elliott: 
 - How can we make Richard and those who agree with him happy?  
 - What project(s) will suffer, more specifically will choose not to upgrade to 
JXPath 1.3 or switch to a different implementation of XPath if we keep 
registerDefaultNamespace()?

Richard: 
 - How can we make Elliott and his cohort happy?
 - What project(s) will suffer, etc. if we revert the change and leave 
registerDefaultNamespace() out? Are there workarounds?

Let's try to find consensus.

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