Cannot Start WebLogic 8.1 After GWT Designer Install

[thug]

I am evaluating GWT Designer, and have run into a serious issue. After installation of Designer via the update site, I can no longer launch WebLogic 8.1 in debug mode in Eclipse. The other developers on the team are also having this problem.

I have done several clean installs of Eclipse, and simply cannot get the two to play nicely together.

After Designer is installed, a NullPointerException is thrown (stack trace and details below). We are using the Oracle plugin for WL downloaded via Eclipse from the Servers tab on the Debug perspective.

Anyone seen this before, or have an idea how to correct the behaviour?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
eclipse.buildId=M20090211-1700
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -clean


Error
Wed Jun 24 14:04:25 EDT 2009
An internal error occurred during: "Starting BEA WebLogic Server v8.1 at localhost".

java.lang.NullPointerException
at oracle.eclipse.tools.weblogic.legacy.GenericWeblogicServerBehaviour.findWorkshopJspDebuggerLaunchConfigurationDelegate(GenericWeblogicServerBehaviour.java:477)
at oracle.eclipse.tools.weblogic.legacy.GenericWeblogicServerBehaviour.setupLaunch(GenericWeblogicServerBehaviour.java:226)
at org.eclipse.jst.server.generic.core.internal.ExternalLaunchConfigurationDelegate.launch(ExternalLaunchConfigurationDelegate.java:97)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:764)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:614)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:607)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:2858)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:2808)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:300)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

[Eric Clayberg]

Based on the exception, it looks very likely that there us a bug in GenericWeblogicServerBehaviour. It is expecting something from a launch configuration, but does not check for null in some case. Maybe it only expects to interact with base Eclipse launch configs and doesn't know how to handle a 3rd party launch config like the one added by GWT Designer.

I can't even begin to guess what the issue might be without seeing what happens in GenericWeblogicServerBehaviour. Since the exception is happening in WebLogic code, it should be reported to them. This problem is very unlikely to be GWT Designer related.