May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3908) NPE creating Top down jax-ws service

by Jan Richter (JIRA)

Jan Richter created JBDS-3908: --------------------------------- Summary: NPE creating Top down jax-ws service Key: JBDS-3908 URL: https://issues.jboss.org/browse/JBDS-3908 Project: Red Hat Developer Studio (DevStudio) Issue Type: Bug Components: webservices Affects Versions: 10.0.0.Alpha2 Reporter: Jan Richter I get this error when trying to create a service from wsdl: {noformat}IWAB0014E Unexpected exception occurred. java.lang.NullPointerException at org.jboss.tools.ws.creation.core.commands.ImplementationClassCreationCommand.execute(ImplementationClassCreationCommand.java:120) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359) at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:437) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:353) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:993) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91) at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:154) at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:869) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) at org.eclipse.jface.window.Window.open(Window.java:794) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) 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.GeneratedMethodAccessor131.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) 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:494) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) 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:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) 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:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519) at org.eclipse.equinox.launcher.Main.main(Main.java:1492){noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3907) NPE when invoking jax-ws service from web service tester

by Jan Richter (JIRA)

Jan Richter created JBDS-3907: --------------------------------- Summary: NPE when invoking jax-ws service from web service tester Key: JBDS-3907 URL: https://issues.jboss.org/browse/JBDS-3907 Project: Red Hat Developer Studio (DevStudio) Issue Type: Bug Components: webservices Affects Versions: 10.0.0.Alpha2 Reporter: Jan Richter I have a project with a jax-ws service deployed on wildfly. Select the service wsdl -> test in jboss web service tester. Clicking invoke shows this error: {noformat} An internal error occurred during: "Invoking web service...". java.lang.NullPointerException at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1909) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1809) at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1726) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3906) Installer does not recognize when the client's connection is severed

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3906?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3906: ----------------------------------- I can get to this state by letting all the vpn based downloads complete and then disconnect from internet. > Installer does not recognize when the client's connection is severed > -------------------------------------------------------------------- > > Key: JBDS-3906 > URL: https://issues.jboss.org/browse/JBDS-3906 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Denis Golovin > > The restart on fail feature only works when: > - connection timeout occurs > - vpn is not active > It does not work, however when: > - client loses internet connection > - read timeout occurs (once connection has been established) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22372) Publish CI snapshots to a directory containing Git branch name

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22372?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22372: ----------------------------------- Summary: Publish CI snapshots to a directory containing Git branch name (was: Publish CI snapshots to a directory containing BUILD_ALIAS) > Publish CI snapshots to a directory containing Git branch name > -------------------------------------------------------------- > > Key: JBIDE-22372 > URL: https://issues.jboss.org/browse/JBIDE-22372 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > To avoid even more "crossing streams", we could consider also adding the BUILD_ALIAS to the URL of snapshots sites produced by CI. An advantage is that building a new version wouldn't require to cleanup the /4.4.neon branch for example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22372) Publish CI snapshots to a directory containing BUILD_ALIAS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22372?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22372: ----------------------------------- Summary: Publish CI snapshots to a directory containing BUILD_ALIAS (was: Publish CI snapshots to a directory containing Git branch name) > Publish CI snapshots to a directory containing BUILD_ALIAS > ---------------------------------------------------------- > > Key: JBIDE-22372 > URL: https://issues.jboss.org/browse/JBIDE-22372 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > To avoid even more "crossing streams", we could consider also adding the BUILD_ALIAS to the URL of snapshots sites produced by CI. An advantage is that building a new version wouldn't require to cleanup the /4.4.neon branch for example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3906) Installer does not recognize when the client's connection is severed

by Jan Richter (JIRA)

Jan Richter created JBDS-3906: --------------------------------- Summary: Installer does not recognize when the client's connection is severed Key: JBDS-3906 URL: https://issues.jboss.org/browse/JBDS-3906 Project: Red Hat Developer Studio (DevStudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.0.0.Alpha1 Reporter: Jan Richter Assignee: Denis Golovin The restart on fail feature only works when: - connection timeout occurs - vpn is not active It does not work, however when: - client loses internet connection - read timeout occurs (once connection has been established) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Thomas Mäder commented on JBDS-3903: ------------------------------------ Honestly, I assumed that the docker tooling was installed by the all-in-one (didn't remember installing it), but I guess I was wrong there, sorry about that. In this case, may I suggest we improve the error message? The error message I get when I press "search" in the new connection dialog is something like "a connection was detected but is not active". When I google for this, I get nothing useful. If we are trying to use an env-var an it is not set, mentioning it would help more with finding out what the problem is. > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: docker, platform-installer > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Denis Golovin > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-713) Implement a test for generating Java <-> WSDL

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-713?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-713: ------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/720, https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/721 > Implement a test for generating Java <-> WSDL > --------------------------------------------- > > Key: JBTIS-713 > URL: https://issues.jboss.org/browse/JBTIS-713 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.3.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-713) Implement a test for generating Java <-> WSDL

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-713?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky resolved JBTIS-713. ------------------------------------- Fix Version/s: 4.3.0.Final Resolution: Done > Implement a test for generating Java <-> WSDL > --------------------------------------------- > > Key: JBTIS-713 > URL: https://issues.jboss.org/browse/JBTIS-713 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.3.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.3.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22419) Deploy Docker Wizard: Connection info looks weird

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22419?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22419: --------------------------------------- It looks weird. Notice the border around the text. It should be similar to service details in New OpenShift Server Adapter wizard, where text is still markable and copyable and it even looks better, because text marked in Deploy Docker Image is not visible (background color of marking is light grey and text become white, so it is not readable), but in the Server Adapter wizard it is blue background with white text. > Deploy Docker Wizard: Connection info looks weird > ------------------------------------------------- > > Key: JBIDE-22419 > URL: https://issues.jboss.org/browse/JBIDE-22419 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Priority: Minor > Labels: docker, openshift_v3 > Fix For: 4.4.x > > Attachments: docker_wizard.png > > > Connection info in Deploy Image to OpenShift wizard looks weird. It is a text widget but it looks like it is text area where it is supposed to be text typed, but it is disabled. It is also possible to put cursor there. This apply both for wizard opened via context menu of a docker image as well as for wizard opened from context menu of an OpenShift project. > !docker_wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2016