[JBoss JIRA] (TEIIDDES-2188) Move the REST Importer out of the XML Importer and into a Separate Importer Option
by Ted Jones (JIRA)
Ted Jones created TEIIDDES-2188:
-----------------------------------
Summary: Move the REST Importer out of the XML Importer and into a Separate Importer Option
Key: TEIIDDES-2188
URL: https://issues.jboss.org/browse/TEIIDDES-2188
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export, Web Services Support
Affects Versions: 8.5
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 8.5.1
Currently the REST importer is included in the XML importer. It should be moved to it's own import option (like SOAP) to make it more obvious. Also, since we are adding JSON support for REST services as sources in Designer, REST won't just be for XML anymore.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2189) Add ModelType validation in the New MED wizard to prevent creating MED without one selected
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2189:
--------------------------------------
Summary: Add ModelType validation in the New MED wizard to prevent creating MED without one selected
Key: TEIIDDES-2189
URL: https://issues.jboss.org/browse/TEIIDDES-2189
Project: Teiid Designer
Issue Type: Enhancement
Components: Extension Framework
Affects Versions: 8.3.2
Reporter: Barry LaFond
Fix For: 8.3.4, 8.5.1
The New MED wizard's 2nd page allows selecting View Model and/or Source Model types. However, if neither is selected, then the MED is created without one and can be confusing and will prevent actually defining MED properties.
Need to add ERROR message and prevent FINISH if this happens.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1829) Add Dynamic Parameter Capability to REST Connection Profile
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1829?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1829:
--------------------------------
Summary: Add Dynamic Parameter Capability to REST Connection Profile (was: Add Dynamic Parameter Capability to REST Importer )
Description: Currently the REST CP just takes a URL, potentially with parameters included. Need to add an option for dynamic parameters including URI and/or query string. As parameters are added, we should generate a preview of the full URL. Something like: http://{host}:{port}/restservice/books/book?parm1=value1&parm2=value2. (was: Currently the REST importer just takes a URL with parameters included. Need to add an option for dynamic parameters. This will mean generating a procedure instead of a table and building the URL dynamically using the passed in values.)
> Add Dynamic Parameter Capability to REST Connection Profile
> -----------------------------------------------------------
>
> Key: TEIIDDES-1829
> URL: https://issues.jboss.org/browse/TEIIDDES-1829
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Web Services Support
> Affects Versions: 8.2
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 8.6, 8.5.1
>
>
> Currently the REST CP just takes a URL, potentially with parameters included. Need to add an option for dynamic parameters including URI and/or query string. As parameters are added, we should generate a preview of the full URL. Something like: http://{host}:{port}/restservice/books/book?parm1=value1&parm2=value2.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2187) Teiid Connection importer- chosing a location isn't filled in unless you hit back button
by Debbie Steigner (JIRA)
Debbie Steigner created TEIIDDES-2187:
-----------------------------------------
Summary: Teiid Connection importer- chosing a location isn't filled in unless you hit back button
Key: TEIIDDES-2187
URL: https://issues.jboss.org/browse/TEIIDDES-2187
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.3.2
Environment: Windows Vista or 2008 Only
Reporter: Debbie Steigner
This only happens when installed on Windows Vista or 2008 not on Linux.
Choose File -> Import -> Teiid Designer -> Teiid Connection >> Source model:
Then, choose a particular data source (shouldn't matter which one)
Click "Next", this screen will now ask you to choose a location
Click on the dots behind the grayed out "Location:" field and choose a location
After selecting a location and pressing the "Ok" button, the location is not taken from the "Select a folder" dialog box and therefore empty.
If I now choose "Back", I arrive in the previous screen again. Pressing "Next" again now does fill in the previously chosen "Location" value.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2182) Issues with Excel import
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2182?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2182:
------------------------------------
Fix Version/s: 8.6
8.5.1
> Issues with Excel import
> ------------------------
>
> Key: TEIIDDES-2182
> URL: https://issues.jboss.org/browse/TEIIDDES-2182
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5, 8.6, 8.5.1
>
> Attachments: excelSheet.ddl
>
>
> See comment on this community thread -
> https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable
> There are a couple of issues with this scenario in Designer:
> 1)
> {code}
> org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
> at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
> at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> {code}
> This is a bug with the array init on line 791 of TeiidImportManager
> 2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.
>
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2182) Issues with Excel import
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2182?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-2182:
-----------------------------------------
Submitted designer pull request. The namespace URI will be the primary mechanism to match the extension property to the Designer MEDs - when the namespace statement is included. For now, we fall back on the prefix mappings - only if the ns uri has not been resolved. i was able to go end to end with the Teiid Connection Importer scenario, but this should be tested further.
> Issues with Excel import
> ------------------------
>
> Key: TEIIDDES-2182
> URL: https://issues.jboss.org/browse/TEIIDDES-2182
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
> Attachments: excelSheet.ddl
>
>
> See comment on this community thread -
> https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable
> There are a couple of issues with this scenario in Designer:
> 1)
> {code}
> org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
> at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
> at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
> {code}
> This is a bug with the array init on line 791 of TeiidImportManager
> 2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.
>
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2186) SWT Illegal Argument exception from Teiid Server Editor page
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2186?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2186:
-----------------------------------
Fix Version/s: 8.3.4
> SWT Illegal Argument exception from Teiid Server Editor page
> ------------------------------------------------------------
>
> Key: TEIIDDES-2186
> URL: https://issues.jboss.org/browse/TEIIDDES-2186
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.5, 8.3.4
>
>
> While using the Teiid Importer for an Infinispan DS received the following, probably unrelated, exception.
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null)
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653)
> 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:140)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
> 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)
> Caused by: java.lang.IllegalArgumentException: Argument cannot be null
> at org.eclipse.swt.SWT.error(SWT.java:4378)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.SWT.error(SWT.java:4283)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2085)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor.refreshDisplayValues(TeiidServerEditor.java:574)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor.access$0(TeiidServerEditor.java:556)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor$1$1.run(TeiidServerEditor.java:148)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 23 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2186) SWT Illegal Argument exception from Teiid Server Editor page
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2186?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2186:
-----------------------------------
Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/commit/c467ee125619c659d...
> SWT Illegal Argument exception from Teiid Server Editor page
> ------------------------------------------------------------
>
> Key: TEIIDDES-2186
> URL: https://issues.jboss.org/browse/TEIIDDES-2186
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.5, 8.3.4
>
>
> While using the Teiid Importer for an Infinispan DS received the following, probably unrelated, exception.
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null)
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653)
> 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:140)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
> 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)
> Caused by: java.lang.IllegalArgumentException: Argument cannot be null
> at org.eclipse.swt.SWT.error(SWT.java:4378)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.SWT.error(SWT.java:4283)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2085)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor.refreshDisplayValues(TeiidServerEditor.java:574)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor.access$0(TeiidServerEditor.java:556)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor$1$1.run(TeiidServerEditor.java:148)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 23 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2186) SWT Illegal Argument exception from Teiid Server Editor page
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2186?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2186.
------------------------------------
Resolution: Done
Added checks to prevent setting text widgets with a NULL string
> SWT Illegal Argument exception from Teiid Server Editor page
> ------------------------------------------------------------
>
> Key: TEIIDDES-2186
> URL: https://issues.jboss.org/browse/TEIIDDES-2186
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> While using the Teiid Importer for an Infinispan DS received the following, probably unrelated, exception.
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null)
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653)
> 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:140)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
> 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)
> Caused by: java.lang.IllegalArgumentException: Argument cannot be null
> at org.eclipse.swt.SWT.error(SWT.java:4378)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.SWT.error(SWT.java:4283)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
> at org.eclipse.swt.widgets.Text.setText(Text.java:2085)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor.refreshDisplayValues(TeiidServerEditor.java:574)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor.access$0(TeiidServerEditor.java:556)
> at org.teiid.designer.runtime.ui.server.editor.TeiidServerEditor$1$1.run(TeiidServerEditor.java:148)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 23 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2017) NPE while using Teiid Connection Importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2017?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2017:
----------------------------------------
Moved the last comment to it's own JIRA (TEIIDDES-2186) and re-resolved this issue
> NPE while using Teiid Connection Importer
> -----------------------------------------
>
> Key: TEIIDDES-2017
> URL: https://issues.jboss.org/browse/TEIIDDES-2017
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.5, 8.3.4
>
>
> While trying to use "Teiid Connection >> Source Model" importer with new SOLR source type I encountered
> {code}
> java.lang.NullPointerException
> at org.teiid.designer.teiidimporter.ui.wizard.ShowDDLPage.setVisible(ShowDDLPage.java:201)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> 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.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> 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.GeneratedMethodAccessor49.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> 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:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> The dialog did not pop any dialog box about error, nor it can proceed any further, so notification given to user other than he/she can cancel it. But the above is logged in the "errors" panel.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 9 months