> I've had my fair share of fun trying to use getResourceBundle > to load a > properties file and made basically the same discoveries you have. The > properties file say bar.properties gets loaded as > ResourceBundle.getBundle("org.foo.bar") and must be in > WEB-INF/classes/org/foo/bar.properties. This is so Tomcat can find the > properties file in the web applications classpath- otherwise it > doesn't know > where it is- When I tried placing the properties file in WEB-INF/classes/com/foo/bar/FooListResourceBundle.properties (to use the naming convention of my example in the post) it was not found. Only when I placed it in $TOMCAT_HOME/classes/com/foo/bar/FooListResourceBundle.properties was it found (but then I got the second error). Jim Dilbert: I *have* a personality! Dogbert: Let's not get into that "Is zero a number" debate again.
- Class loader behavior with resource bundles... James Lehmer
- Re: Class loader behavior with resource bundles..... Jason Novotny
- Re: Class loader behavior with resource bundl... Craig R. McClanahan
- RE: Class loader behavior with resource b... James Lehmer
- Sharing Servlet between Web Applications Wyn Easton
- Re: Sharing Servlet between Web Applicati... Bo Xu
- Re: Sharing Servlet between Web Applicati... Craig R. McClanahan
- How to re-use a request scope bean? James Lehmer
- How to re-use a request scope bean? Todd Chaffee
- Re: How to re-use a request scope bea... Joe Emenaker
- Re: How to re-use a request scop... Todd Chaffee
- RE: Class loader behavior with resource bundles..... William Kaufman
- RE: Class loader behavior with resource bundl... James Lehmer
- RE: Class loader behavior with resource bundles..... Kulkarni, Narayana
- RE: Class loader behavior with resource bundles..... DONNIE HALE
- RE: Class loader behavior with resource bundl... James Lehmer