[jbosstools-issues] [JBoss JIRA] (JBIDE-21451) Application wizard: No projects nor server templates when launched from explorer context menu

Marián Labuda (JIRA) issues at jboss.org
Fri Apr 29 08:15:03 EDT 2016


     [ https://issues.jboss.org/browse/JBIDE-21451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marián Labuda closed JBIDE-21451.
---------------------------------


Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5255.

> Application wizard: No projects nor server templates when launched from explorer context menu
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-21451
>                 URL: https://issues.jboss.org/browse/JBIDE-21451
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.Beta2
>            Reporter: Marián Labuda
>            Assignee: Andre Dietisheim
>              Labels: application_wizard, openshift_v3
>             Fix For: 4.4.0.Alpha1
>
>         Attachments: empty_project.png
>
>
> Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
> !empty_project.png!
> This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
> Stack trace:
> {code}
> org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> 	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> 	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> 	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> 	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> 	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> 	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> 	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> 	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> 	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> 	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> 	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> 	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> 	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> 	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> 	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> 	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> 	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> 	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> 	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> 	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> 	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:497)
> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> 	at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> 	at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
> 	at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
> 	at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> 	at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 	at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:497)
> 	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> 	... 38 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jbosstools-issues mailing list