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=42157>. 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=42157 ------- Additional Comments From [EMAIL PROTECTED] 2007-04-18 08:23 ------- Ok, the lack of directory listing support i understand. But as for the URI.resolve... i do not understand. Shouldn't a URL be URI "compatible"... the error happens because the getResource returns one of these: "jndi:/servername//WEB-INF/" shouldn't it be more like "jndi://servername/WEB-INF/" as most URLs, it makes sense and URIs would work fine. And i'am running this over a "a regular file environment", bellow is the HOST element that I'm using in server.xml. <Host name="alphabit" unpackWARs="false" appBase="/data/http/"> <Context path="/" docBase="KISSLet"/> </Host> (In reply to comment #1) > This will not be addressed (toURI().resolve is useless, and getInputStream > for a > folder is a proprietary capability). When running Tomcat over a regular file > based environment, it will return file: URL, but if you keep to normal URL > manipulation, you may use it over non file based repositories. (In reply to comment #1) > This will not be addressed (toURI().resolve is useless, and getInputStream > for a > folder is a proprietary capability). When running Tomcat over a regular file > based environment, it will return file: URL, but if you keep to normal URL > manipulation, you may use it over non file based repositories. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
