Angso, Tony wrote: > Am using RAD6 (Websphere6) That's basically Eclipse. Yak ;-)
> The class path is both in .ClassPath file and also configured in > Websphere JVM classPath Don't define classes in the JVM classpath. If you are implementing a web application, put the JARs in WEB-INF/lib/. If it's an ear, there is another level in the ear file where you can put the JARs. If you put something like commons-logging too high up into the classloader hierarchy, for example above log4j, it is likely to try and reference classes via the thread context classloader for which it cannot resolve the dependencies correctly. hope that helps, Roland > <classpathentry exported="true" kind="lib" > path="C:/Tony/Download/Java/log4j/apache-log4j-1.2.15/log4j-1.2.15.jar"/ > <classpathentry exported="true" kind="lib" > path="C:/Tony/Download/Java/shared/jars/commons-logging-1.1.jar"/> > <classpathentry exported="true" kind="lib" > path="C:/Tony/Download/Java/shared/jars/commons-codec-1.3.jar"/> > <classpathentry exported="true" kind="lib" > path="C:/Tony/Download/Java/shared/jars/commons-httpclient-3.1.jar"/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
