geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Delos Dai (JIRA)" <>
Subject [jira] Commented: (GERONIMODEVTOOLS-536) Fail to launch browser when run a dynamic web application on server via GEP
Date Thu, 27 Nov 2008 02:04:46 GMT


Delos Dai commented on GERONIMODEVTOOLS-536:

I found this extension declare in plugin.xml of

 <extension point="org.eclipse.wst.server.core.launchableAdapters">

In fact, the server adapter id should be unique.The id "org.eclipse.jst.server.generic.web"
has been used by a built-in generic server adapter of WTP. With the same id, it's not sure
which adapter is got by WTP. So sometimes if generic server adapter is got by WTP while a
browser needs to be launched, no module is bound with  generic server adapter. It's the reason
why an NullPointException is thrown here.

I think we can give an unique id here.Maybe we can change the id into "org.eclipse.jst.server.geronimo.web".
I have verified this change locally.

Attachment is the patch for this defect.Could anyone help to review it?

Thanks a lot!

> Fail to launch browser when run a dynamic web application on server via GEP
> ---------------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-536
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>         Environment: OS:Windows
>            Reporter:
>            Assignee: Tim McConnell
>            Priority: Minor
> Steps:
> 1.Open a clean eclipse, and then install GEP, define a server
> 2.Create a dynamic web application, and right-click "run on server"
> 3.No browser popups, and you will see error"Error opening browser" on "Error log" tab
at the bottom of eclipse.
> Error in elicpse: 
> 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

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

View raw message