DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21857>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21857 document() takes cocoon:/xxx as relative URI ------- Additional Comments From [EMAIL PROTECTED] 2003-07-24 17:29 ------- I tried now with CVS too. The href is still prepended by the stylesheets path. Here is what the tomcat log tells: using xalan-2.3.1: XSLTProcessorImpl: resolve(href = cocoon:/menu-adrim.xml, base = null); using xalan-2.5.1: XSLTProcessorImpl: resolve(href = file:/usr/share/tomcat4/webapps/cocoon-2.1/adron/stylesheets/cocoon:/menu-.xml, base = null); using xalan-2.5.1-cvs: XSLTProcessorImpl: resolve(href = file:/usr/share/tomcat4/webapps/cocoon2.1/adron/stylesheets/cocoon:/menu-.xml, base = null); If I use (with 2.5.1-cvs) document('http:/menu-.xml') instead of document('cocoon:/menu-.xml), the following is in the log: XSLTProcessorImpl: resolve(href = http:/menu-.xml, base = null); This makes me thinking, that some URIs are recognized and handled as absolute paths. I can understand that cocoon:/ doesn't count as a 'wellknown' URI. But I guess there are other cases where uncommon protocols will be used, so there should be a more sophisticated handler.
