November 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-678) Issues after Refactoring Source Model Name

by Ted Jones (JIRA)

Issues after Refactoring Source Model Name ------------------------------------------ Key: TEIIDDES-678 URL: https://jira.jboss.org/browse/TEIIDDES-678 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.1 Reporter: Ted Jones I have three VDB's... all with the same three models in them with different combinations of visibility. 1. BQT (Source Model) 2. PART (Source Model) 3. VIRT (View Model) If I re-factor the PART model name to PARTS I see the following: 1. My transformation query changed from SELECT * FROM PART.PARTS to SELECT * FROM PARTS.PARTSS 2. I can't consistently produce this one, but the third or first VDB has the new model name added but leaves the old one as well. So I end up with a PART and a PARTS. 3. When I click the synch button on PART in the vdb editor, I get an illegal argument exception. 4. When I try to remove PART, the VIRT model gets removed to because the Designer thinks there is still a dependency on PART by VIRT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-700) An index on a view table can be created, but opening its transformation diagram gets an exception

by Paul Nittel (JIRA)

An index on a view table can be created, but opening its transformation diagram gets an exception ------------------------------------------------------------------------------------------------- Key: TEIIDDES-700 URL: https://jira.jboss.org/browse/TEIIDDES-700 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1.1 Reporter: Paul Nittel Fix For: 7.1.1 At this time there should be no transformation diagram for an index on a view relational model. Error 2010-11-04 12:36:37.652 Problems occurred when invoking code from plug-in: "org.eclipse.jface". java.lang.IllegalArgumentException: TransformationHelper.getTransformationMappingRoot:null or invalid target. at com.metamatrix.modeler.internal.transformation.util.TransformationHelper.getTransformationMappingRoot(TransformationHelper.java:2574) at com.metamatrix.modeler.internal.transformation.util.TransformationHelper.getTransformationMappingRoot(TransformationHelper.java:2622) at com.metamatrix.modeler.transformation.ui.diagram.TransformationDiagramType.canOpenContext(TransformationDiagramType.java:147) at com.metamatrix.modeler.diagram.ui.DiagramTypeManager.canOpenContext(DiagramTypeManager.java:190) at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.canOpenContext(DiagramEditor.java:265) at com.metamatrix.modeler.internal.ui.editors.ModelEditor.openModelObject(ModelEditor.java:972) at com.metamatrix.modeler.internal.ui.editors.ModelEditor.openModelObject(ModelEditor.java:947) at com.metamatrix.modeler.ui.editors.ModelEditorManager$5.run(ModelEditorManager.java:239) at com.metamatrix.ui.internal.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:80) at com.metamatrix.modeler.ui.editors.ModelEditorManager.open(ModelEditorManager.java:234) at com.metamatrix.modeler.internal.ui.explorer.ModelExplorerResourceNavigator$5.doubleClick(ModelExplorerResourceNavigator.java:637) at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:824) 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.fireDoubleClick(StructuredViewer.java:822) at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1421) at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1225) at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:238) at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:235) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:296) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
2
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-30) Saving the "Model" does not save un-saved transformation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-30?page=com.atlassian.jira.plugin.... ] Barry LaFond resolved TEIIDDES-30. ---------------------------------- Resolution: Done handleSqlEditorEvent() method was ignoring any event from itself, but it needed to at least check that the eventType == CHANGES_PENDING. Added the logic and now the page is properly set to dirty for any SQL change resulting in saving the SQL prior to Saving Model Editor. > Saving the "Model" does not save un-saved transformation > -------------------------------------------------------- > > Key: TEIIDDES-30 > URL: https://jira.jboss.org/browse/TEIIDDES-30 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 7.1.1 > > > When you added a transformation, there is "save/validate" button on the transformation editor for saving the transformation. However, instead of that button you used the model save button on the top tool bar, this does not save the transformation. > 1) At this point if you exit the designer it does not warn you that I have a unsaved transformation > 2) once the designer re-started the transformation is gone. > I think saving the model should save any other editors underneath that model. > (IGNORE...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Reopened: (TEIIDDES-30) Saving the "Model" does not save un-saved transformation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-30?page=com.atlassian.jira.plugin.... ] Barry LaFond reopened TEIIDDES-30: ---------------------------------- Checked again and did reproduce. > Saving the "Model" does not save un-saved transformation > -------------------------------------------------------- > > Key: TEIIDDES-30 > URL: https://jira.jboss.org/browse/TEIIDDES-30 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 7.1.1 > > > When you added a transformation, there is "save/validate" button on the transformation editor for saving the transformation. However, instead of that button you used the model save button on the top tool bar, this does not save the transformation. > 1) At this point if you exit the designer it does not warn you that I have a unsaved transformation > 2) once the designer re-started the transformation is gone. > I think saving the model should save any other editors underneath that model. > (IGNORE...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-541) Table data preview requires all models in project to be without validation errors - should pertain only to models required for preview

by Paul Nittel (JIRA)

Table data preview requires all models in project to be without validation errors - should pertain only to models required for preview -------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-541 URL: https://jira.jboss.org/browse/TEIIDDES-541 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, Teiid 7.1M1 Reporter: Paul Nittel Attachments: LogWithPreviewErrors.log While in the middle of creating a virtual model, I attempted to preview data from an imported source model. Because the virtual model was incomplete, and thus failed validation, the preview was not possible. This is a valid use case. Preview of a model's tables should always work assuming invalid models are not required for the preview itself. Attaching the Designer's log file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

4
6
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-30) Saving the "Model" does not save un-saved transformation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-30?page=com.atlassian.jira.plugin.... ] Barry LaFond resolved TEIIDDES-30. ---------------------------------- Resolution: Cannot Reproduce Bug Cannot reproduce. > Saving the "Model" does not save un-saved transformation > -------------------------------------------------------- > > Key: TEIIDDES-30 > URL: https://jira.jboss.org/browse/TEIIDDES-30 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 7.1.1 > > > When you added a transformation, there is "save/validate" button on the transformation editor for saving the transformation. However, instead of that button you used the model save button on the top tool bar, this does not save the transformation. > 1) At this point if you exit the designer it does not warn you that I have a unsaved transformation > 2) once the designer re-started the transformation is gone. > I think saving the model should save any other editors underneath that model. > (IGNORE...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-656) Teiid Designer perspective is not opened or selected after New Model is created from non-Designer perpective.

by Barry LaFond (JIRA)

Teiid Designer perspective is not opened or selected after New Model is created from non-Designer perpective. ------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-656 URL: https://jira.jboss.org/browse/TEIIDDES-656 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1, 7.1.1 Reporter: Barry LaFond Priority: Critical Fix For: 7.2 If working in a multi-perspective use-case, users may create Teiid Designer projects and create Metadata Models without opening the Teiid Designer perspective. New Models are automatically opened in a Model Editor, which is good (unless user has changed the default editor for ".xmi" files) However the bulk of the model editing framework is tied to the "Model Explorer". We should provide a dialog that can query the user to "Open" or "Switch" to the Designer perspective and this dialog should include a "Don't ask me this again" check-box (preference boolean) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-684) Unable to import projects created by MetaMatrix 5.5.x

by Paul Nittel (JIRA)

Unable to import projects created by MetaMatrix 5.5.x ----------------------------------------------------- Key: TEIIDDES-684 URL: https://jira.jboss.org/browse/TEIIDDES-684 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1.1 Environment: Windows XP, JBDS 4.0 Beta 1 Reporter: Paul Nittel Fix For: 7.1.1 Attachments: 001_DataSourceModelingLab_CompletedProjectSet.zip Importing a Model Project Set (MPS) from the MetaMatrix 5.5.4 Getting Start Guide tutorials yields no visible results, no errors, but a phantom project exists in the workspace. Trying to import the project from an unzipped MPS provides better results, but I found one of the relational source models was consistently corrupt. Perhaps things aren't as bleak as they seem, but this all needs to be clearer for the "hapless user". (I'll attach the MPS.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

3
12
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-18) UnsupportedOperationException when importing from Rose

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-18?page=com.atlassian.jira.plugin.... ] Barry LaFond resolved TEIIDDES-18. ---------------------------------- Resolution: Duplicate Issue Same as TEIIDDES-314 > UnsupportedOperationException when importing from Rose > ------------------------------------------------------ > > Key: TEIIDDES-18 > URL: https://jira.jboss.org/browse/TEIIDDES-18 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Environment: fedora 10 > Reporter: Paul Nittel > Fix For: Future > > Attachments: PartsSupplierLogical.mdl > > > I tried to import PartsSupplierLogical.mdl (attached) and received this exception: > !ENTRY com.metamatrix.rose 4 0 2008-12-15 10:55:10.304 > !MESSAGE java.lang.UnsupportedOperationException > !STACK 0 > java.lang.UnsupportedOperationException > at org.eclipse.uml2.common.util.DerivedEObjectEList$DerivedListIterator.add(DerivedEObjectEList.java:278) > at java.util.AbstractSequentialList.add(AbstractSequentialList.java:129) > at org.eclipse.uml2.common.util.DerivedEObjectEList.addUnique(DerivedEObjectEList.java:636) > at org.eclipse.uml2.common.util.DerivedEObjectEList.add(DerivedEObjectEList.java:623) > at java.util.AbstractList.add(AbstractList.java:91) > at com.metamatrix.rose.internal.handler.UmlHandler.createPackage(UmlHandler.java:773) > at com.metamatrix.rose.internal.handler.AbstractRoseHandler.visitObject(AbstractRoseHandler.java:261) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:45) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseList(RoseWalker.java:52) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:67) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:40) > at com.metamatrix.rose.internal.RoseImporter.parseUnits(RoseImporter.java:876) > at com.metamatrix.rose.internal.RoseImporter.parseSelectedUnits(RoseImporter.java:605) > at com.metamatrix.rose.internal.ui.wizard.RoseImportWizard$4.run(RoseImportWizard.java:362) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > Dec 15, 2008 10:55:09.870 [ModalContext|0] ERROR <com.metamatrix.rose|0> java.lang.UnsupportedOperationException > java.lang.UnsupportedOperationException > at org.eclipse.uml2.common.util.DerivedEObjectEList$DerivedListIterator.add(DerivedEObjectEList.java:278) > at java.util.AbstractSequentialList.add(AbstractSequentialList.java:129) > at org.eclipse.uml2.common.util.DerivedEObjectEList.addUnique(DerivedEObjectEList.java:636) > at org.eclipse.uml2.common.util.DerivedEObjectEList.add(DerivedEObjectEList.java:623) > at java.util.AbstractList.add(AbstractList.java:91) > at com.metamatrix.rose.internal.handler.UmlHandler.createPackage(UmlHandler.java:773) > at com.metamatrix.rose.internal.handler.AbstractRoseHandler.visitObject(AbstractRoseHandler.java:261) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:45) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseList(RoseWalker.java:52) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:67) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:40) > at com.metamatrix.rose.internal.RoseImporter.parseUnits(RoseImporter.java:876) > at com.metamatrix.rose.internal.RoseImporter.parseSelectedUnits(RoseImporter.java:605) > at com.metamatrix.rose.internal.ui.wizard.RoseImportWizard$4.run(RoseImportWizard.java:362) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > While it appears to continue, if you clickpast the exception, it just hangs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-314) UnsupportedOperationException importing Rose Model

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-314?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-314: ---------------------------------- Assignee: (was: Dan Florian) Fix Version/s: Future EMF upgrades have resulting in the Rose Importer being non-functional. This feature has been included in MMX product versions, but there is no known community/users at this time. Pushing out to re-visit in future if users need it. > UnsupportedOperationException importing Rose Model > -------------------------------------------------- > > Key: TEIIDDES-314 > URL: https://jira.jboss.org/browse/TEIIDDES-314 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Reporter: Barry LaFond > Fix For: Future > > > Importing Rose Model results in following exception: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2010