geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donald Woods (JIRA)" <>
Subject [jira] Updated: (GERONIMODEVTOOLS-209) Hello World JSP does not open in Eclipse browser when invoked with "run as, run on server" from within Eclipse
Date Wed, 19 Sep 2007 16:26:12 GMT


Donald Woods updated GERONIMODEVTOOLS-209:

    Affects Version/s:     (was: 2.1)
        Fix Version/s:     (was: 2.1)

This affects the 2.0.0 plugin and should be fixed ASAP in a 2.0.x plugin release, so we can
support Geronimo 2.0 deployment plans.
Also, please try to keep the first 2 digits of a plugin release in sync with the Geornimo
Server, which we haven't done in the past and caused great user confusion....

> Hello World JSP does not open in Eclipse browser when invoked with "run as, run on server"
from within Eclipse
> --------------------------------------------------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-209
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.0
>            Reporter: Tim McConnell
>            Assignee: Tim McConnell
>             Fix For: 2.0.x
> This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The Eclipse
plugin is passing a valid HttpLaunchable object, with the correct url, to the WTP web client
launcher class ([org.eclipse.wst.server.ui.web). But when it is ultimately ready to be launched
that launchable object is null causing a NPE (stack trace below). Moving the JIRA to 2.1,
and will open a bugzilla report against WTP 2.0.x.
> java.lang.NullPointerException
> 	at org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(
> 	at org.eclipse.wst.server.core.internal.Client.launch(
> 	at org.eclipse.wst.server.ui.internal.LaunchClientJob$
> 	at
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(
> 	at org.eclipse.swt.widgets.Display.runAsyncMessages(
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(
> 	at org.eclipse.ui.internal.Workbench.runUI(
> 	at org.eclipse.ui.internal.Workbench.access$4(
> 	at org.eclipse.ui.internal.Workbench$
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
> 	at org.eclipse.ui.internal.ide.application.IDEApplication.start(
> 	at
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
> 	at
> 	at
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at org.eclipse.equinox.launcher.Main.invokeFramework(
> 	at org.eclipse.equinox.launcher.Main.basicRun(
> 	at
> 	at org.eclipse.equinox.launcher.Main.main(

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message