Here's a workaround:

You have to adjust your project to force the naughty weblogic jars to appear AFTER the JDK 1.3 jars on your project's classpath. The easiest way to do this is to go into the JDK 1.3 definition itself, and add the weblogic jars to the JDK's list of jars, AFTER all the real JDK jars.

Do this under Tools/Configure JDK, select the JDK your project is using, and add the weblogic jar(s) to that JDK's own list of jars. Make sure to put them at the END of the list, so that the compiler will find the good 1.3 classes before it finds the bad 1.2.2 classes.

Then, delete the weblogic jars from your project's required libraries settings.

DO NOT edit jbuilder4/bin/jdk.config to do this. jdk.config controls the JVM under which JBuilder itself runs. What you have to fix is the classpath under which your project itself runs.
2001-Jan-10 5:32pm gyles19@visi.com

  Are there any tools available to help diagnose classpath problems?