http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1976 *** shadow/1976 Sun Jun 3 00:44:19 2001 --- shadow/1976.tmp.23788 Sun Jun 10 11:34:08 2001 *************** *** 5,11 **** | Status: NEW Version: 2.0.x | | Resolution: Platform: PC | | Severity: Normal OS/Version: All | ! | Priority: Component: Xalan | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | --- 5,11 ---- | Status: NEW Version: 2.0.x | | Resolution: Platform: PC | | Severity: Normal OS/Version: All | ! | Priority: High Component: Xalan | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | *************** *** 33,35 **** --- 33,52 ---- Figuring out what version of which library was used for any "product" version is very time consuming and seems to be "never ending" from an integrators point of view :-( + + ------- Additional Comments From [EMAIL PROTECTED] 2001-06-10 11:34 ------- + You are correct that Appendix B of the DOM spec refers to a package name of + org.w3c.dom.ranges and XalanJ uses a name of org.w3c.dom.range. Earlier drafts + of the DOM spec used the singular and that is, perhaps, where XalanJ got it + from. + + In any event, I agree that this is very confusing and reconciling these + differences is one of the main goals of the xml-commons project. I have + forwarded this bug over to the commons-dev mailing list so that they are aware + of this discrepancy. Once the commons project has settled on the common + classes, we will retrofit XalanJ to use them and this problem will go away. + + I apologize for the confusion in the meantime. + + Thank you very much for noting this problem and bringing it to our attention. + It is greatly appreciated. \ No newline at end of file
