|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 892 | minor | always | 01-20-06 09:30 | 01-24-06 16:01 | |
|
|
|||||
| Reporter: | anonymous | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.0.17 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.18 | ||
|
|
|||||
| Summary: | 0000892: BundleTag does not find resources in jar files | ||||
| Description: |
We recently moved our resource property files into jar files and our <fmt:bundle> lookups stopped working. Here is what the code looked like: <fmt:bundle basename="fully.qualified.path.CommonMessages"> This does not work when our property files are in jars. |
||||
| Steps To Reproduce: | |||||
| Additional Information: |
Tracked it down to BundleManager line 214: InputStream is = loader.getResourceAsStream(name.replace('.', '/') + ".properties"); Properties files in jar files need a leading '/'. The workaround is to write the resource lookup with '/my.full.path.MyBundle', which is ugly but works. Adding this line just after 214 should fix it: if (is == null) { is = loader.getResourceAsStream('/' + name.replace('.', '/') + ".properties"); } |
||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||