Yes I saw that. In the case of the sun jdk if no value was set actually java.endorsed.dirs had a default value i.e lib\endorsed but the IBM one had a value of null. Of course nowhere is it mentioned that it can't be null and still the Java 2 Platform looks for JAR files in the default standard location. So if the IBM JDK does that when java.endorsed.dirs is null then it is not a JDK bug.
Regards Manu On 9/6/07, Karan Malhi <[EMAIL PROTECTED]> wrote: > >as java.endorsed.dirs should not be null. > I think it can be null. Here is some text from the javadocs: > > If no value is set for java.endorsed.dirs, then Sun Microsystem's > implementation of the Java 2 Platform looks for JAR files in a default > standard location: > > <java-home>\lib\endorsed [Microsoft Windows] > <java-home>/lib/endorsed [Solaris or Linux] > > Here <java-home> refers to the directory where the runtime software is > installed (which is the top-level directory of the Java 2 Runtime > Environment or the jre directory in the Java 2 SDK). > > The Java runtime environment will use classes in such JAR files to > override the corresponding classes provided in the Java 2 Platform as > shipped by Sun. > -- > Karan Singh Malhi >
