PM
| To: Tomcat Developers List
| Subject: Re: 3.3 classloading & resources
|
|
| The solution - for JDK1.2+ - is to use the 3 parameter getBundle, with
| Thread.currentThread().getContextClassLoader() as the third param.
| For JDK1.1 there's nothing you can do.
|
| Let me know if it doe
The problem is that ResourceBundle is kindof broken. Like many other
java APIs ( JAXP, JNDI, URL, etc ), early versions are not capable
of using the application class loader.
This is ( IMHO ) a bug, and for some APIs it is fixed ( JAXP and JNDI for
sure, unfortunately not for URL ).
The solution
and in IBM WebSphere 3.5.4
and it has worked in both.
I hope this has helped.
-Mike
- Original Message -
From: "Keith Wannamaker" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Monday, November 26, 2001 2:44 PM
Subject: 3.3 classlo
I think there may be a problem with resource loading in TC3.3.
If I add a property file to the app class path by setting
org.apache.tomcat.apps.classpath, then the call to
ResourceBundle.getBundle("foo") doesn't find it. Nor does
it get located if I place the said property file in tomcat/lib/ap
