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=22777>. 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=22777 Error resolving imports/includes with a baseURI of a full Windows path ------- Additional Comments From [EMAIL PROTECTED] 2003-09-02 21:29 ------- It looks like I understand the common problem we have. The problem is that we cannot use java.net.URI because it was implemented only in Java 1.4. We use org.apache.xml.utils.SystemIDResolver which doesn't have full functionality (e.g. we are not verifying if a string is a valid URI). Not having such functionality we are not doing good job setting SystemID (in particular in org.apache.xalan.xslt.Process). We can have 2 solutions 1. To write code similar to java.net.URI one (which is time consuming). 2. Continue to use the SystemIDResolver, wait until we wouldn't need to support Java versions older than 1.4 and rewrite the code using the java.net.URI. For the time being I am making a small fix in the SystemIDResolver.
