[JBoss JIRA] (JBIDE-18007) Server adapter: Incorrect error message when deleting application via server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18007:
-------------------------------------
Description:
After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
!delete_app_via_adapter.png!
We should either:
1) Fix error message and behaviour to delete also a project in workspace. But I think this is not desired solution, bcs. user would want to work with his project later, although it has been deleted from OpenShift.
2.) Fix behaviour to delete also the project from workspace and error message will be fully correct.
was:
After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
!delete_app_via_adapter.png!
We should either:
1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
2.) Fix behaviour to delete also the project from workspace and error message will be fully correct.
> Server adapter: Incorrect error message when deleting application via server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-18007
> URL: https://issues.jboss.org/browse/JBIDE-18007
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter
> Attachments: delete_app_via_adapter.png
>
>
> After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
> However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
> !delete_app_via_adapter.png!
> We should either:
> 1) Fix error message and behaviour to delete also a project in workspace. But I think this is not desired solution, bcs. user would want to work with his project later, although it has been deleted from OpenShift.
> 2.) Fix behaviour to delete also the project from workspace and error message will be fully correct.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18007) Server adapter: Deletion of an application via server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18007:
-------------------------------------
Description:
After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
!delete_app_via_adapter.png!
We should either:
1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
2.) Fix behaviour to delete also an application from workspace and error message will be fully correct.
was:
After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about application in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the application in the workspace. It only delete an application on OpenShift server.
However, trying to delete an OpenShift application via adapter with non-existing application in workspace (but existing on OpenShift) this error message is correct.
!delete_app_via_adapter.png!
We should either:
1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
2.) Fix behaviour to delete also an application from workspace and error message will be fully correct.
> Server adapter: Deletion of an application via server adapter
> -------------------------------------------------------------
>
> Key: JBIDE-18007
> URL: https://issues.jboss.org/browse/JBIDE-18007
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter
> Attachments: delete_app_via_adapter.png
>
>
> After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
> However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
> !delete_app_via_adapter.png!
> We should either:
> 1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
> 2.) Fix behaviour to delete also an application from workspace and error message will be fully correct.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18007) Server adapter: Incorrect error message when deleting application via server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18007:
-------------------------------------
Summary: Server adapter: Incorrect error message when deleting application via server adapter (was: Server adapter: Deletion of an application via server adapter)
> Server adapter: Incorrect error message when deleting application via server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-18007
> URL: https://issues.jboss.org/browse/JBIDE-18007
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter
> Attachments: delete_app_via_adapter.png
>
>
> After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
> However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
> !delete_app_via_adapter.png!
> We should either:
> 1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
> 2.) Fix behaviour to delete also an application from workspace and error message will be fully correct.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18007) Server adapter: Incorrect error message when deleting application via server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18007:
-------------------------------------
Labels: server_adapter (was: )
> Server adapter: Incorrect error message when deleting application via server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-18007
> URL: https://issues.jboss.org/browse/JBIDE-18007
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter
> Attachments: delete_app_via_adapter.png
>
>
> After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
> However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
> !delete_app_via_adapter.png!
> We should either:
> 1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
> 2.) Fix behaviour to delete also an application from workspace and error message will be fully correct.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18007) Server adapter: Incorrect error message when deleting application via server adapter
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18007?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18007:
-------------------------------------
Description:
After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
!delete_app_via_adapter.png!
We should either:
1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
2.) Fix behaviour to delete also the project from workspace and error message will be fully correct.
was:
After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
!delete_app_via_adapter.png!
We should either:
1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
2.) Fix behaviour to delete also an application from workspace and error message will be fully correct.
> Server adapter: Incorrect error message when deleting application via server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-18007
> URL: https://issues.jboss.org/browse/JBIDE-18007
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter
> Attachments: delete_app_via_adapter.png
>
>
> After attempt to delete non-existing application via server adapter there is a error message telling us about non-existing application but also about project in workspace. This is not quite correct, bcs. delete application through server adapter does not provide removal of the project in the workspace. It only deletes an application on OpenShift.
> However, trying to delete an OpenShift application via adapter with non-existing project in workspace (but existing on OpenShift) this error message is correct.
> !delete_app_via_adapter.png!
> We should either:
> 1) Fix error message and behaviour to delete also an application in workspace. But I think this is not desired solution, bcs. user would want to work with his application later, although it has been deleted from OpenShift.
> 2.) Fix behaviour to delete also the project from workspace and error message will be fully correct.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18031) Widget disposed error when toggling EA features on/off
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18031?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18031:
-----------------------------------
Description:
1. Install JBT 4.2.0.Beta3 or CR1 (nightly) into Eclipse Luna eclipse-jee-luna-R-linux.gtk.x86_64.tar.gz
2. Launch JBT, and Central will open by itself (default)
3. Select Software/Update tab
4. Close Central
(So far, so good.)
5. Reopen it from the coolbar icon.
7. Select "Show Early Access" checkbox (enable or disable, whichever shows that same issue)
Pop-up:
{code}
Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
{code}
Stack:
{code}
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4441)
at org.eclipse.swt.SWT.error(SWT.java:4356)
at org.eclipse.swt.SWT.error(SWT.java:4327)
at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:562)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$1.propertyChange(JBossCentralEditor.java:533)
at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:382)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:378)
at org.eclipse.ui.preferences.ScopedPreferenceStore$2.preferenceChange(ScopedPreferenceStore.java:197)
at org.eclipse.core.internal.preferences.EclipsePreferences$3.run(EclipsePreferences.java:896)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:899)
at org.eclipse.core.internal.preferences.EclipsePreferences.putBoolean(EclipsePreferences.java:926)
at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:553)
at org.jboss.tools.central.editors.SoftwarePage.access$11(SoftwarePage.java:506)
at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:236)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
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:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
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:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
Environment:
{code}
eclipse.buildId=4.4.0.I20140606-1215
java.version=1.8.0
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -showLocation -Dorg.jboss.tools.vpe.loadxulrunner=false
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product -clean -showLocation -data /home/nboldt/eclipse/workspace-clean44 -consolelog -console -debug -Dorg.jboss.tools.vpe.loadxulrunner=false
{code}
Restarting Eclipse/JBDS "resets" the error so first Central page works fine, but the bug is still there for next times you'll open Central.
was:
1. Install JBT 4.2.0.Beta3 or CR1 (nightly) into Eclipse Luna eclipse-jee-luna-R-linux.gtk.x86_64.tar.gz
2. Launch JBT, and Central will open by itself (default)
3. Select Software/Update tab
4. Enable the "Enable Early Access" box, and click "Yes" to accept.
5. Disable the "Enable Early Access" box, and click "OK" to acknowledge.
(So far, so good.)
6. Close Central, then reopen it from the coolbar icon.
7. Repeat steps 4 and 5. This time, you will see errors such as this:
{code}
Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
{code}
{code}
org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:4441)
at org.eclipse.swt.SWT.error(SWT.java:4356)
at org.eclipse.swt.SWT.error(SWT.java:4327)
at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:562)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$1.propertyChange(JBossCentralEditor.java:533)
at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:382)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:378)
at org.eclipse.ui.preferences.ScopedPreferenceStore$2.preferenceChange(ScopedPreferenceStore.java:197)
at org.eclipse.core.internal.preferences.EclipsePreferences$3.run(EclipsePreferences.java:896)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:899)
at org.eclipse.core.internal.preferences.EclipsePreferences.putBoolean(EclipsePreferences.java:926)
at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:553)
at org.jboss.tools.central.editors.SoftwarePage.access$11(SoftwarePage.java:506)
at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:236)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
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:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
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:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
{code}
{code}
eclipse.buildId=4.4.0.I20140606-1215
java.version=1.8.0
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product -showLocation -Dorg.jboss.tools.vpe.loadxulrunner=false
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product -clean -showLocation -data /home/nboldt/eclipse/workspace-clean44 -consolelog -console -debug -Dorg.jboss.tools.vpe.loadxulrunner=false
{code}
8. Restart Eclipse. Errors go away. (Steps 4-5 work as expected.)
9. Close and re-open Central. Errors are back. (Steps 4-5 throw errors.)
> Widget disposed error when toggling EA features on/off
> ------------------------------------------------------
>
> Key: JBIDE-18031
> URL: https://issues.jboss.org/browse/JBIDE-18031
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, discovery
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR1
>
>
> 1. Install JBT 4.2.0.Beta3 or CR1 (nightly) into Eclipse Luna eclipse-jee-luna-R-linux.gtk.x86_64.tar.gz
> 2. Launch JBT, and Central will open by itself (default)
> 3. Select Software/Update tab
> 4. Close Central
> (So far, so good.)
> 5. Reopen it from the coolbar icon.
> 7. Select "Show Early Access" checkbox (enable or disable, whichever shows that same issue)
> Pop-up:
> {code}
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> {code}
> Stack:
> {code}
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:476)
> at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:562)
> at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$1.propertyChange(JBossCentralEditor.java:533)
> at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:382)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:378)
> at org.eclipse.ui.preferences.ScopedPreferenceStore$2.preferenceChange(ScopedPreferenceStore.java:197)
> at org.eclipse.core.internal.preferences.EclipsePreferences$3.run(EclipsePreferences.java:896)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.preferences.EclipsePreferences.firePreferenceEvent(EclipsePreferences.java:899)
> at org.eclipse.core.internal.preferences.EclipsePreferences.putBoolean(EclipsePreferences.java:926)
> at org.jboss.tools.central.editors.SoftwarePage.handleEarlyAccessChanged(SoftwarePage.java:553)
> at org.jboss.tools.central.editors.SoftwarePage.access$11(SoftwarePage.java:506)
> at org.jboss.tools.central.editors.SoftwarePage$5.widgetSelected(SoftwarePage.java:236)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> 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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
> Environment:
> {code}
> eclipse.buildId=4.4.0.I20140606-1215
> java.version=1.8.0
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product -showLocation -Dorg.jboss.tools.vpe.loadxulrunner=false
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product -clean -showLocation -data /home/nboldt/eclipse/workspace-clean44 -consolelog -console -debug -Dorg.jboss.tools.vpe.loadxulrunner=false
> {code}
> Restarting Eclipse/JBDS "resets" the error so first Central page works fine, but the bug is still there for next times you'll open Central.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-8531) WSDL files should be accessible to BPEL project from another project (without copying)
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8531?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky closed JBIDE-8531.
------------------------------------
Verified with JBDS-IS 7.0.2.GA / JBTIS 4.1.5.Final
How it works:
1. You are allowed to import WSDL from another project
2. You will see the following error message
"The import location of ../../Math/bpelContent/MathArtifacts.wsdl is not supported by this implementation. Import artifacts must be contained within the folder hierarchy that has the deployment descriptor at the root"
3. This is ok, you can work with such wsdl in your project
4. Before deploying fix the wsdl location so that it is contained in your project
5. The error message disappears
> WSDL files should be accessible to BPEL project from another project (without copying)
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-8531
> URL: https://issues.jboss.org/browse/JBIDE-8531
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: bpel
> Affects Versions: 3.2.0.CR1
> Environment: all
> Reporter: Robert (Bob) Brodt
> Assignee: Robert (Bob) Brodt
> Fix For: 3.3.0.CR1-SOA, LATER
>
>
> SOA-P 5.2 PRD document requirement SOA-TOOL-2:
> The SOA-5.2 PRD requirements include the ability of a BPEL project to reference WSDLs (and probably XSDs as well) in another project without having to make copies. The assumption is that all resources are in the same eclipse workspace, not in a file system folder or remote server.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months