[JBoss JIRA] (TEIIDDES-1059) RFE for Teiid Designer - add a new importer similar to the Text File importer but for XML Documents
by Barry LaFond (Updated) (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1059?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1059:
-----------------------------------
Attachment: (was: teiid-xml-file-source-page-2.png)
> RFE for Teiid Designer - add a new importer similar to the Text File importer but for XML Documents
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1059
> URL: https://issues.jboss.org/browse/TEIIDDES-1059
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 7.6
>
> Attachments: employee_info.xml, medsamp2011.xml, teiid-data-file-import-options.png, teiid-flat-file-source-page-1.png, teiid-flat-file-source-page-2.png, teiid-flat-file-source-page-3.png, teiid-xml-file-source-page-1.png, teiid-xml-file-source-page-2.png, teiid-xml-file-source-page-3.png
>
>
> Can an Importer similar to the text file importer be added to Teiid Designer. One that would produce the same results as if it was manually done.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1059) RFE for Teiid Designer - add a new importer similar to the Text File importer but for XML Documents
by Barry LaFond (Updated) (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1059?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1059:
-----------------------------------
Attachment: teiid-xml-file-source-page-2.png
> RFE for Teiid Designer - add a new importer similar to the Text File importer but for XML Documents
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1059
> URL: https://issues.jboss.org/browse/TEIIDDES-1059
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 7.6
>
> Attachments: employee_info.xml, medsamp2011.xml, teiid-data-file-import-options.png, teiid-flat-file-source-page-1.png, teiid-flat-file-source-page-2.png, teiid-flat-file-source-page-3.png, teiid-xml-file-source-page-1.png, teiid-xml-file-source-page-2.png, teiid-xml-file-source-page-3.png
>
>
> Can an Importer similar to the text file importer be added to Teiid Designer. One that would produce the same results as if it was manually done.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1059) RFE for Teiid Designer - add a new importer similar to the Text File importer but for XML Documents
by Barry LaFond (Updated) (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1059?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1059:
-----------------------------------
Attachment: (was: teiid-flat-file-type-selection-page.png)
> RFE for Teiid Designer - add a new importer similar to the Text File importer but for XML Documents
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1059
> URL: https://issues.jboss.org/browse/TEIIDDES-1059
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 7.6
>
> Attachments: employee_info.xml, medsamp2011.xml, teiid-data-file-import-options.png, teiid-flat-file-source-page-1.png, teiid-flat-file-source-page-2.png, teiid-flat-file-source-page-3.png, teiid-flat-file-source-target-page.png, teiid-xml-data-file-import-source-page.png, teiid-xml-file-source-page-1.png, teiid-xml-file-source-page-2.png, teiid-xml-file-source-page-3.png
>
>
> Can an Importer similar to the text file importer be added to Teiid Designer. One that would produce the same results as if it was manually done.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1059) RFE for Teiid Designer - add a new importer similar to the Text File importer but for XML Documents
by Barry LaFond (Updated) (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1059?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1059:
-----------------------------------
Attachment: (was: teiid-xml-data-file-import-settings.png)
> RFE for Teiid Designer - add a new importer similar to the Text File importer but for XML Documents
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1059
> URL: https://issues.jboss.org/browse/TEIIDDES-1059
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Import/Export
> Affects Versions: 7.5
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 7.6
>
> Attachments: employee_info.xml, medsamp2011.xml, teiid-data-file-import-options.png, teiid-flat-file-source-page-1.png, teiid-flat-file-source-page-2.png, teiid-flat-file-source-page-3.png, teiid-flat-file-source-target-page.png, teiid-xml-data-file-import-source-page.png, teiid-xml-file-source-page-1.png, teiid-xml-file-source-page-2.png, teiid-xml-file-source-page-3.png
>
>
> Can an Importer similar to the text file importer be added to Teiid Designer. One that would produce the same results as if it was manually done.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1122) Add/Remove operations on a VDB should block other operations on the VDB
by Van Halbert (Created) (JIRA)
Add/Remove operations on a VDB should block other operations on the VDB
-----------------------------------------------------------------------
Key: TEIIDDES-1122
URL: https://issues.jboss.org/browse/TEIIDDES-1122
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.4.2
Reporter: Marc Shirley
Assignee: Barry LaFond
As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: 0
at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
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$6.handleEvent(ActionContributionItem.java:452)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
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:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB
by Van Halbert (Updated) (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ]
Van Halbert updated TEIIDDES-1118:
----------------------------------
Affects Version/s: 7.4.2
(was: 7.5)
> Add/Remove operations on a VDB should block other operations on the VDB
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1118
> URL: https://issues.jboss.org/browse/TEIIDDES-1118
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 7.4.2
> Reporter: Marc Shirley
> Assignee: Barry LaFond
>
> As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
> at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
> at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
> at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> 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$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> 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:369)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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:620)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB
by Marc Shirley (Commented) (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ]
Marc Shirley commented on TEIIDDES-1118:
----------------------------------------
This also appears to be non-latency related, but rather a failure to resolve dependencies when using a UNC path. Re-testing with UNC, the indexes appear to never be created when a model is added to the VDB, and the dependencies appear not to be resolved. I tested adding a model that required 3 other models to a VDB, and the index files were not created when I checked the file system 2 hours later. The required models were also not added to the VDB.
> Add/Remove operations on a VDB should block other operations on the VDB
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1118
> URL: https://issues.jboss.org/browse/TEIIDDES-1118
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 7.5
> Reporter: Marc Shirley
> Assignee: Barry LaFond
>
> As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
> at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
> at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
> at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> 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$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> 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:369)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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:620)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB
by Marc Shirley (Commented) (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ]
Marc Shirley commented on TEIIDDES-1118:
----------------------------------------
Further testing shows this may only occur when using UNC path format. Same location with the network filesystem mapped to a drive letter in a Windows environment results in the operations succeeding and the exception being avoided.
> Add/Remove operations on a VDB should block other operations on the VDB
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1118
> URL: https://issues.jboss.org/browse/TEIIDDES-1118
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 7.5
> Reporter: Marc Shirley
> Assignee: Barry LaFond
>
> As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
> at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
> at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
> at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> 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$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> 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:369)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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:620)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB
by Barry LaFond (Moved) (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ]
Barry LaFond moved JBDS-1895 to TEIIDDES-1118:
----------------------------------------------
Project: Teiid Designer (was: Developer Studio (JBoss Developer Studio))
Key: TEIIDDES-1118 (was: JBDS-1895)
Affects Version/s: 7.5
(was: 4.1.0.GA)
Component/s: VDB & Execution
(was: teiid)
Security: (was: Public)
> Add/Remove operations on a VDB should block other operations on the VDB
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1118
> URL: https://issues.jboss.org/browse/TEIIDDES-1118
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 7.5
> Reporter: Marc Shirley
> Assignee: Barry LaFond
>
> As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
> at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
> at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
> at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> 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$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> 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:369)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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:620)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months