[JBoss JIRA] (JBDS-1266) Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBDS-1266?page=com.atlassian.jira.plugin.... ]
Koen Aers commented on JBDS-1266:
---------------------------------
I assume that this issue doesn't need a fix anymore. If it is still important feel free to reopen so we can assess priority.
> Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-1266
> URL: https://issues.jboss.org/browse/JBDS-1266
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration-platform, jbpm, runtime
> Affects Versions: 3.0.0.GA
> Environment: Version: 3.0.0.GA
> Build id: v201003100055R
> Build date: 201003100222
> Reporter: Len DiMaggio
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.x
>
> Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The sequence of events is:
> 1) Create a jBPM project
> 2) Successfully test the connection to a SOA-P server
> 3) Select credentials checkbox - enter invalid credentials
> 4) Deploy the jBPM project process - the deployment will use the credentials previously used during the test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBDS-1266) Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBDS-1266?page=com.atlassian.jira.plugin.... ]
Koen Aers resolved JBDS-1266.
-----------------------------
Resolution: Out of Date
> Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-1266
> URL: https://issues.jboss.org/browse/JBDS-1266
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration-platform, jbpm, runtime
> Affects Versions: 3.0.0.GA
> Environment: Version: 3.0.0.GA
> Build id: v201003100055R
> Build date: 201003100222
> Reporter: Len DiMaggio
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.x
>
> Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The sequence of events is:
> 1) Create a jBPM project
> 2) Successfully test the connection to a SOA-P server
> 3) Select credentials checkbox - enter invalid credentials
> 4) Deploy the jBPM project process - the deployment will use the credentials previously used during the test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBDS-1266) Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBDS-1266?page=com.atlassian.jira.plugin.... ]
Koen Aers updated JBDS-1266:
----------------------------
Component/s: jbpm
> Credentials entered to test jBPM process deployment are cached - not over-ridden if user enters different credentials to deploy a process
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-1266
> URL: https://issues.jboss.org/browse/JBDS-1266
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration-platform, jbpm, runtime
> Affects Versions: 3.0.0.GA
> Environment: Version: 3.0.0.GA
> Build id: v201003100055R
> Build date: 201003100222
> Reporter: Len DiMaggio
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.x
>
> Attachments: Screenshot-1.png, Screenshot-2.png, Screenshot.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> The sequence of events is:
> 1) Create a jBPM project
> 2) Successfully test the connection to a SOA-P server
> 3) Select credentials checkbox - enter invalid credentials
> 4) Deploy the jBPM project process - the deployment will use the credentials previously used during the test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15505) exception in jaxrs at startup
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15505?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-15505:
-------------------------------------
Assignee: Max Rydahl Andersen (was: Xavier Coulon)
Please review the PR
> exception in jaxrs at startup
> -----------------------------
>
> Key: JBIDE-15505
> URL: https://issues.jboss.org/browse/JBIDE-15505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> Not sure how I got the error, but I just restarted a workspace after deleting some projects in previous session.
> At startup I got this error:
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.dispose(UriMappingsContentProvider.java:116)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider$1.run(SafeDelegateTreeContentProvider.java:76)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.dispose(SafeDelegateTreeContentProvider.java:74)
> at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension$3.run(NavigatorContentExtension.java:210)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension.dispose(NavigatorContentExtension.java:207)
> at org.eclipse.ui.internal.navigator.NavigatorContentService.dispose(NavigatorContentService.java:355)
> at org.eclipse.ui.navigator.CommonViewer.dispose(CommonViewer.java:251)
> at org.eclipse.ui.navigator.CommonViewer.handleDispose(CommonViewer.java:239)
> at org.eclipse.jface.viewers.ContentViewer$2.widgetDisposed(ContentViewer.java:214)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1308)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:910)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1311)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:910)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1311)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.disposeWidget(SWTPartRenderer.java:152)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.disposeWidget(ContributedPartRenderer.java:273)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:899)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.disposeWidget(ElementReferenceRenderer.java:109)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:899)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1598)
> at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:1231)
> at org.eclipse.ui.internal.WorkbenchWindow.access$14(WorkbenchWindow.java:1198)
> at org.eclipse.ui.internal.WorkbenchWindow$10.run(WorkbenchWindow.java:1261)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1259)
> at org.eclipse.ui.internal.Workbench$14.run(Workbench.java:1096)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1079)
> at org.eclipse.ui.internal.Workbench.access$19(Workbench.java:1024)
> at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1327)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1325)
> at org.eclipse.ui.internal.Workbench.restart(Workbench.java:2480)
> at org.eclipse.ui.internal.handlers.RestartWorkbenchHandler.execute(RestartWorkbenchHandler.java:31)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15505) exception in jaxrs at startup
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15505?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15505:
----------------------------------
Fix Version/s: 4.2.0.Alpha1
> exception in jaxrs at startup
> -----------------------------
>
> Key: JBIDE-15505
> URL: https://issues.jboss.org/browse/JBIDE-15505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> Not sure how I got the error, but I just restarted a workspace after deleting some projects in previous session.
> At startup I got this error:
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.dispose(UriMappingsContentProvider.java:116)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider$1.run(SafeDelegateTreeContentProvider.java:76)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.dispose(SafeDelegateTreeContentProvider.java:74)
> at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension$3.run(NavigatorContentExtension.java:210)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension.dispose(NavigatorContentExtension.java:207)
> at org.eclipse.ui.internal.navigator.NavigatorContentService.dispose(NavigatorContentService.java:355)
> at org.eclipse.ui.navigator.CommonViewer.dispose(CommonViewer.java:251)
> at org.eclipse.ui.navigator.CommonViewer.handleDispose(CommonViewer.java:239)
> at org.eclipse.jface.viewers.ContentViewer$2.widgetDisposed(ContentViewer.java:214)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1308)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:910)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1311)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:910)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1311)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.disposeWidget(SWTPartRenderer.java:152)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.disposeWidget(ContributedPartRenderer.java:273)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:899)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.disposeWidget(ElementReferenceRenderer.java:109)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:899)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1598)
> at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:1231)
> at org.eclipse.ui.internal.WorkbenchWindow.access$14(WorkbenchWindow.java:1198)
> at org.eclipse.ui.internal.WorkbenchWindow$10.run(WorkbenchWindow.java:1261)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1259)
> at org.eclipse.ui.internal.Workbench$14.run(Workbench.java:1096)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1079)
> at org.eclipse.ui.internal.Workbench.access$19(Workbench.java:1024)
> at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1327)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1325)
> at org.eclipse.ui.internal.Workbench.restart(Workbench.java:2480)
> at org.eclipse.ui.internal.handlers.RestartWorkbenchHandler.execute(RestartWorkbenchHandler.java:31)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15597 at 10/9/13 5:28 AM:
-------------------------------------------------------------------
[~mwigglesworth-redhat]: having double expansion like you suggest seems not a good idea imho. This is very uncommon for Eclipse. I suggest you put it into the "Advanced" section. Having the table in the page makes the page grow beyond acceptable size (it's already very very crowded). I therefore added a shortened label that tells one that there are env variables set. You can edit them and get to the table UI by hitting "Edit..." (see !Environmental%20Variables%20UI%20WorkFlow.png!)
was (Author: adietish):
[~mwigglesworth-redhat]: having double expansion like you suggest seems not a good idea imho. This is very uncommon for Eclipse. I suggest you put it into the "Advanced" section. Having the table in the page makes the page grow beyond acceptable size (it's already very very crowded). I therefore added a shortened label that tells one that there are env variables set. You can edit them and get to the table UI by hitting "Edit..." (see balsamiq [^Environmental%20Variables%20UI%20WorkFlow.png])
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15597 at 10/9/13 5:28 AM:
-------------------------------------------------------------------
[~mwigglesworth-redhat]: having double expansion like you suggest seems not a good idea imho. This is very uncommon for Eclipse. I suggest you put it into the "Advanced" section. Having the table in the page makes the page grow beyond acceptable size (it's already very very crowded). I therefore added a shortened label that tells one that there are env variables set. You can edit them and get to the table UI by hitting "Edit..." (see !Environmental Variables UI WorkFlow.png!)
was (Author: adietish):
[~mwigglesworth-redhat]: having double expansion like you suggest seems not a good idea imho. This is very uncommon for Eclipse. I suggest you put it into the "Advanced" section. Having the table in the page makes the page grow beyond acceptable size (it's already very very crowded). I therefore added a shortened label that tells one that there are env variables set. You can edit them and get to the table UI by hitting "Edit..." (see !Environmental%20Variables%20UI%20WorkFlow.png!)
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15597:
------------------------------------------
[~mwigglesworth-redhat]: having double expansion like you suggest seems not a good idea imho. This is very uncommon for Eclipse. I suggest you put it into the "Advanced" section. Having the table in the page makes the page grow beyond acceptable size (it's already very very crowded). I therefore added a shortened label that tells one that there are env variables set. You can edit them and get to the table UI by hitting "Edit..." (see balsamiq [^Environmental%20Variables%20UI%20WorkFlow.png])
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15613) Error: Failed to send reload command to browser
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15613?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-15613:
-------------------------------------
Assignee: Max Rydahl Andersen (was: Xavier Coulon)
Please review the PR
Relevant part is https://github.com/jbosstools/jbosstools-livereload/pull/63/files#diff-ff...
Other changes are for logs (adjusting level and messages) and fixing the JUnit tests to count the number of notification received by the client.
> Error: Failed to send reload command to browser
> -----------------------------------------------
>
> Key: JBIDE-15613
> URL: https://issues.jboss.org/browse/JBIDE-15613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.1.Alpha2
> Environment: JBT Alpha2-v20131002-1827-B444, Linux 64bit, Java 6
> Reporter: Vlado Pakan
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.1.1.Beta1
>
>
> 1. Import HTML 5 project from Central
> 2. Run it on server
> 3. Open project in Web Browser with LiveReload via Server View
> 4. Update and save index.html file many times
> ASSERT: Changes to index.html are reflected in Web Browser
> ERROR: This error appear in Error Log:
> Failed to send reload command to browser
> {noformat}
> java.io.IOException: closedOut 1001:null
> at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameConnection.sendMessage(WebSocketConnectionRFC6455.java:437)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.sendMessage(LiveReloadWebSocket.java:97)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.inform(LiveReloadWebSocket.java:177)
> at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:57)
> at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.publishFinished(ServerLifeCycleListener.java:131)
> at org.eclipse.wst.server.core.internal.Server.firePublishFinished(Server.java:1150)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3176)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15613) Error: Failed to send reload command to browser
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15613?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15613:
----------------------------------
Fix Version/s: 4.2.0.Alpha1
> Error: Failed to send reload command to browser
> -----------------------------------------------
>
> Key: JBIDE-15613
> URL: https://issues.jboss.org/browse/JBIDE-15613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.1.Alpha2
> Environment: JBT Alpha2-v20131002-1827-B444, Linux 64bit, Java 6
> Reporter: Vlado Pakan
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> 1. Import HTML 5 project from Central
> 2. Run it on server
> 3. Open project in Web Browser with LiveReload via Server View
> 4. Update and save index.html file many times
> ASSERT: Changes to index.html are reflected in Web Browser
> ERROR: This error appear in Error Log:
> Failed to send reload command to browser
> {noformat}
> java.io.IOException: closedOut 1001:null
> at org.eclipse.jetty.websocket.WebSocketConnectionRFC6455$WSFrameConnection.sendMessage(WebSocketConnectionRFC6455.java:437)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.sendMessage(LiveReloadWebSocket.java:97)
> at org.jboss.tools.livereload.core.internal.server.jetty.LiveReloadWebSocket.inform(LiveReloadWebSocket.java:177)
> at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:57)
> at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.publishFinished(ServerLifeCycleListener.java:131)
> at org.eclipse.wst.server.core.internal.Server.firePublishFinished(Server.java:1150)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3176)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months