Is it the responsibility of Tomcat, the application running on Tomcat,
or Java to translate or resolve Windows file paths? If it is Tomcat, does Tomcat 5.0.12 translate or resolve these pathnames
correctly? VQWiki (http://www.croninsolutions.com/veryquickwiki/), a
JSP Wiki engine, when run on Tomcat 5.0.9 on Linux, works as expected.
However, on Tomcat 5.0.12 on Windows XP, VQWiki is unable to find and
save its property file, even though this file exists and is both
readable and writable. VQWiki generates the following report page:
The error had the following message:C:\Program%20Files\Apache%20Software%20Foundation\Tomcat%205.0\w ebapps\vqwiki\WEB-INF\classes\vqwiki.properties (The system cannot find the path specified)
The only way you can get a properly URL encoded URL is when you call getResource on the classloader. If you do a diff, you'll see there's no relevant changes that have been made to the classloader between 5.0.9 and 5.0.12.
The most likely cause is that you don't have spaces in your Tomcat path on Linux, but you do on Windows.
Note: The URL encoding of those paths is a "feature" which could be removed (it is supposed to fix problems with RMI).
-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxx Rémy Maucherat Senior Developer & Consultant JBoss Group (Europe) SàRL xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]