Anonymous | Login | Signup for a new account | 12-17-2024 08:48 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000892 | [Resin] | minor | always | 01-20-06 09:30 | 01-24-06 16:01 | ||||
Reporter | anonymous | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 3.0.17 | ||||||
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. |
||||||||
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"); } |
||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 26 unique queries executed. |