|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4411 | minor | always | 02-25-11 16:50 | 03-02-11 16:08 | |
|
|
|||||
| Reporter: | ccwf | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.15 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.16 | ||
|
|
|||||
| Summary: | 0004411: Wildcarded ServletContext Resource Issues with Spring | ||||
| Description: | Spring ServletContext resources using wildcards do not work with Resin 4.0.15. They worked in 4.0.14. | ||||
| Steps To Reproduce: | |||||
| Additional Information: |
This issue is similar to old bug 0002659, although this problem is with ServletContext resources. The problem is that for wildcarded resources, Spring passes the directory to ServletContext.getResource(String). Resin 4.0.15's ServletContextImpl implementation checks if the requested resource is a file and returns null for directories. Spring's ServletContextResource.getURL method (called from PathMatchingResourcePatternResolver) then throws an exception because it got a null back from ServletContext.getResource(String). Resin 4.0.14's ServletContextImpl only checked that the requested resource exists and did not require it to be a file, so it did not have this interoperability problem with Spring. Here's a typical error produced when using Resin 4.0.15 with Spring and wilcarded resources: [11-02-25 16:13:20.359] {main} org.springframework.beans.factory.BeanDefinitionStoreException: Could not resolve bean definition resource pattern [/WEB-INF/context/*.xml]; nested exception is java.io.FileNotFoundException: ServletContext resource [/WEB-INF/context/] cannot be resolved to URL because it does not exist |
||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||