| Summary: | Jetty fails to start when temporary directory path contains space and extractWAR=false | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Cédric Chabanois <cchabanois> |
| Component: | server | Assignee: | Michael Gorovoy <mgorovoy> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | jetty-inbox, mgorovoy |
| Version: | unspecified | ||
| Target Milestone: | 7.0.2.RC0 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Cédric Chabanois
It took me a while to track this one down because I've been initially chasing it in the wrong direction (lesson learned...) but at the end of the day (literally...) it turned out to be a very simple fix by replacing a call to File.toUrl() with a call to File.getCanonicalPath() that ultimately takes advantage of path encoding by Resource.newResource() implementation. Committed r2002. |