[JBoss JIRA] (TEIIDDES-2009) NPE deleting model objects
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2009?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2009.
------------------------------------
Resolution: Done
Added eObject.eIsProxy() check to prevent NPE. DONE
> NPE deleting model objects
> --------------------------
>
> Key: TEIIDDES-2009
> URL: https://issues.jboss.org/browse/TEIIDDES-2009
> Project: Teiid Designer
> Issue Type: …
[View More]Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
>
> Deleted objects with a model editor open and got following:
> {code}
> java.lang.NullPointerException
> at org.teiid.designer.ui.viewsupport.ModelUtilities.getModelName(ModelUtilities.java:497)
> at org.teiid.designer.ui.table.ModelRowElement.getValue(ModelRowElement.java:335)
> at org.teiid.designer.ui.table.ModelTableLabelProvider.getColumnText(ModelTableLabelProvider.java:40)
> at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:70)
> at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
> at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:400)
> at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
> at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:278)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:758)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:650)
> at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:637)
> at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:593)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
> at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:591)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690)
> at org.teiid.designer.ui.table.ModelObjectTableModel.buildColumns(ModelObjectTableModel.java:273)
> at org.teiid.designer.ui.table.ModelObjectTableModel.buildColumns(ModelObjectTableModel.java:214)
> at org.teiid.designer.ui.table.ModelObjectTableModel.removeRows(ModelObjectTableModel.java:326)
> at org.teiid.designer.ui.table.TableNotificationHandler.handleSingleEObjectNotification(TableNotificationHandler.java:264)
> at org.teiid.designer.ui.table.TableNotificationHandler.handleSingleNotification(TableNotificationHandler.java:202)
> at org.teiid.designer.ui.table.TableNotificationHandler.handleNotification(TableNotificationHandler.java:175)
> at org.teiid.designer.ui.table.TableNotificationHandler.notifyChanged(TableNotificationHandler.java:82)
> at org.teiid.designer.ui.editors.ModelEditor$5.run(ModelEditor.java:1157)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.ui.actions.workers.DeleteWorker.executeCommand(DeleteWorker.java:211)
> at org.teiid.designer.ui.actions.workers.DeleteWorker.execute(DeleteWorker.java:131)
> at org.teiid.designer.ui.actions.ModelObjectAction.doRun(ModelObjectAction.java:62)
> at org.teiid.designer.ui.actions.DeleteEObjectAction.doRun(DeleteEObjectAction.java:88)
> at org.teiid.designer.ui.common.actions.AbstractAction$1.run(AbstractAction.java:544)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.ui.common.actions.AbstractAction.run(AbstractAction.java:547)
> at org.teiid.designer.ui.actions.DeleteAction.doRun(DeleteAction.java:335)
> {code}
--
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
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2008) When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2008?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2008:
-----------------------------------
Assignee: Mark Drilling (was: Barry LaFond)
> When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape
> -----------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2008
> URL: …
[View More]https://issues.jboss.org/browse/TEIIDDES-2008
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Mark Drilling
> Priority: Blocker
>
> - For the new Teiid Connection importer, add a warning if the user is trying
> to use it for specific JDBC translator types. In this warning, make the
> recommendation that they should use our standard JBDC importer. However, if
> they wish to proceed to use this importer, that they should reference the
> documentation as to the source model properties that can be used to control
> the importing.
> - As is being done for translator types MongoDB and LDAP, we will also exclude the ability to import using ModeShape. If ModeShape, then indicate they should use the ModeShape importer.
--
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
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2008) When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2008?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2008:
-----------------------------------
Fix Version/s: 8.3.x
> When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape
> -----------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2008
> URL: https://issues.jboss.org/…
[View More]browse/TEIIDDES-2008
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Mark Drilling
> Priority: Blocker
> Fix For: 8.3.x
>
>
> - For the new Teiid Connection importer, add a warning if the user is trying
> to use it for specific JDBC translator types. In this warning, make the
> recommendation that they should use our standard JBDC importer. However, if
> they wish to proceed to use this importer, that they should reference the
> documentation as to the source model properties that can be used to control
> the importing.
> - As is being done for translator types MongoDB and LDAP, we will also exclude the ability to import using ModeShape. If ModeShape, then indicate they should use the ModeShape importer.
--
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
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2009) NPE deleting model objects
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2009:
--------------------------------------
Summary: NPE deleting model objects
Key: TEIIDDES-2009
URL: https://issues.jboss.org/browse/TEIIDDES-2009
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 8.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 8.3.x
Deleted objects with a model editor open and got …
[View More]following:
{code}
java.lang.NullPointerException
at org.teiid.designer.ui.viewsupport.ModelUtilities.getModelName(ModelUtilities.java:497)
at org.teiid.designer.ui.table.ModelRowElement.getValue(ModelRowElement.java:335)
at org.teiid.designer.ui.table.ModelTableLabelProvider.getColumnText(ModelTableLabelProvider.java:40)
at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:70)
at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:400)
at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:278)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:758)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:650)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:637)
at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:593)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404)
at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:591)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690)
at org.teiid.designer.ui.table.ModelObjectTableModel.buildColumns(ModelObjectTableModel.java:273)
at org.teiid.designer.ui.table.ModelObjectTableModel.buildColumns(ModelObjectTableModel.java:214)
at org.teiid.designer.ui.table.ModelObjectTableModel.removeRows(ModelObjectTableModel.java:326)
at org.teiid.designer.ui.table.TableNotificationHandler.handleSingleEObjectNotification(TableNotificationHandler.java:264)
at org.teiid.designer.ui.table.TableNotificationHandler.handleSingleNotification(TableNotificationHandler.java:202)
at org.teiid.designer.ui.table.TableNotificationHandler.handleNotification(TableNotificationHandler.java:175)
at org.teiid.designer.ui.table.TableNotificationHandler.notifyChanged(TableNotificationHandler.java:82)
at org.teiid.designer.ui.editors.ModelEditor$5.run(ModelEditor.java:1157)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
at org.teiid.designer.ui.actions.workers.DeleteWorker.executeCommand(DeleteWorker.java:211)
at org.teiid.designer.ui.actions.workers.DeleteWorker.execute(DeleteWorker.java:131)
at org.teiid.designer.ui.actions.ModelObjectAction.doRun(ModelObjectAction.java:62)
at org.teiid.designer.ui.actions.DeleteEObjectAction.doRun(DeleteEObjectAction.java:88)
at org.teiid.designer.ui.common.actions.AbstractAction$1.run(AbstractAction.java:544)
at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
at org.teiid.designer.ui.common.actions.AbstractAction.run(AbstractAction.java:547)
at org.teiid.designer.ui.actions.DeleteAction.doRun(DeleteAction.java:335)
{code}
--
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
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2008) When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2008:
-------------------------------------
Summary: When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape
Key: TEIIDDES-2008
URL: https://issues.jboss.org/browse/TEIIDDES-2008
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 8.4
Reporter: Van Halbert
Assignee: Barry …
[View More]LaFond
Priority: Blocker
- For the new Teiid Connection importer, add a warning if the user is trying
to use it for specific JDBC translator types. In this warning, make the
recommendation that they should use our standard JBDC importer. However, if
they wish to proceed to use this importer, that they should reference the
documentation as to the source model properties that can be used to control
the importing.
- As is being done for translator types MongoDB and LDAP, we will also exclude the ability to import using ModeShape. If ModeShape, then indicate they should use the ModeShape importer.
--
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
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2008) When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2008?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration updated TEIIDDES-2008:
----------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1046501
> When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape
> ----------------------------------------------------------------------------------------------…
[View More]-------
>
> Key: TEIIDDES-2008
> URL: https://issues.jboss.org/browse/TEIIDDES-2008
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 8.4
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
>
> - For the new Teiid Connection importer, add a warning if the user is trying
> to use it for specific JDBC translator types. In this warning, make the
> recommendation that they should use our standard JBDC importer. However, if
> they wish to proceed to use this importer, that they should reference the
> documentation as to the source model properties that can be used to control
> the importing.
> - As is being done for translator types MongoDB and LDAP, we will also exclude the ability to import using ModeShape. If ModeShape, then indicate they should use the ModeShape importer.
--
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
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2007) Add page to Teiid Connection importer to optionally show dynamic VDB xml contents before FINISH
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2007?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2007:
--------------------------------------
Assignee: Barry LaFond (was: Mark Drilling)
> Add page to Teiid Connection importer to optionally show dynamic VDB xml contents before FINISH
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2007
> URL: https://…
[View More]issues.jboss.org/browse/TEIIDDES-2007
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export, Teiid Integration
> Affects Versions: 8.3.x
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.3.x
>
>
> Teiid Connection Importer generates a dynamic vdb.xml file that's deployed to access/retrieve DDL for the deployed datasource, then undeployed after import is complete.
> Because of the nature/maturity of this importer and the ability to apply importer properties (name-value), it would be beneficial to add a optional page that displayed the generated dynamic vdb.xml contents.
> 1) Users could hit NEXT > to view the xml or click FINISH if instead.
> 2) Make xml text selectable/copyable to system clipboard
--
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
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2007) Add page to Teiid Connection importer to optionally show dynamic VDB xml contents before FINISH
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2007?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2007:
-----------------------------------
Description:
Teiid Connection Importer generates a dynamic vdb.xml file that's deployed to access/retrieve DDL for the deployed datasource, then undeployed after import is complete.
Because of the nature/maturity of this importer and the ability to apply importer properties (name-value), it would be beneficial to add a optional page …
[View More]that displayed the generated dynamic vdb.xml contents.
1) Users could hit NEXT > to view the xml or click FINISH if instead.
2) Make xml text selectable/copyable to system clipboard
was:
Teiid Connection Importer generates a dynamic vdb.xml file that's deployed to access/retrieve DDL for the deployed datasource, then undeployed after import is complete.
Because of the nature/maturity of this importer and the ability to apply importer properties (name-value), it would be beneficial to add a optional page that displayed the generated dynamic vdb.xml contents.
Users could hit NEXT > to view the xml or click FINISH if instead.
> Add page to Teiid Connection importer to optionally show dynamic VDB xml contents before FINISH
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2007
> URL: https://issues.jboss.org/browse/TEIIDDES-2007
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export, Teiid Integration
> Affects Versions: 8.3.x
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 8.3.x
>
>
> Teiid Connection Importer generates a dynamic vdb.xml file that's deployed to access/retrieve DDL for the deployed datasource, then undeployed after import is complete.
> Because of the nature/maturity of this importer and the ability to apply importer properties (name-value), it would be beneficial to add a optional page that displayed the generated dynamic vdb.xml contents.
> 1) Users could hit NEXT > to view the xml or click FINISH if instead.
> 2) Make xml text selectable/copyable to system clipboard
--
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
[View Less]
11 years, 2 months
[JBoss JIRA] (TEIIDDES-2007) Add page to Teiid Connection importer to optionally show dynamic VDB xml contents before FINISH
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2007:
--------------------------------------
Summary: Add page to Teiid Connection importer to optionally show dynamic VDB xml contents before FINISH
Key: TEIIDDES-2007
URL: https://issues.jboss.org/browse/TEIIDDES-2007
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export, Teiid Integration
Affects Versions: 8.3.x
Reporter: Barry LaFond
…
[View More]Assignee: Mark Drilling
Fix For: 8.3.x
Teiid Connection Importer generates a dynamic vdb.xml file that's deployed to access/retrieve DDL for the deployed datasource, then undeployed after import is complete.
Because of the nature/maturity of this importer and the ability to apply importer properties (name-value), it would be beneficial to add a optional page that displayed the generated dynamic vdb.xml contents.
Users could hit NEXT > to view the xml or click FINISH if instead.
--
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
[View Less]
11 years, 2 months