October 2010 - teiid-designer-issues

[JBoss JIRA] Updated: (TEIIDDES-394) Association between a model and a connector binding for use by the Preview functionality should be stored within the model

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-394?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-394: ---------------------------------- Fix Version/s: 7.1 (was: No Future) > Association between a model and a connector binding for use by the Preview functionality should be stored within the model > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-394 > URL: https://jira.jboss.org/browse/TEIIDDES-394 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Environment: Designer 5.5.3 > Reporter: Greg Haber > Assignee: Barry LaFond > Priority: Minor > Fix For: 7.1 > > > The proposal here is that a weak association between a model and the connector binding it is associated with for design time preview functionality should be stored in the model file itself, and used to re-establish the association for preview functionality when that model is brought into Designer (such as when an import of a Model Project Set is performed). > The association would be stored in the model with a minimum of information (just the binding name), and the proposed logic is that if there is already an existing binding in Designer with name matching that in the model file, the association for Preview will be automatically established with that binding. > I have attached an e-mail thread between me and rreddy on this topic. > One wrinkle here (not explicitly discussed in the e-mail thread) is if the referenced binding in the model does not previously exist in the Designer workspace, but _is_ defined by a VDB contained in the same model project set, and feature JBEDSP-287 is implemented (so that such VDB binding definitions do get brought in during import). It would be good if the association for Preview functionality between model and binding could also be re-established in this case. This would presumably require that the import of a model project set first import any VDBs before it imported design time models. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-368) Designer: Refine the 'pre-View' action's enablement logic

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-368?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-368: ---------------------------------- Fix Version/s: 7.1.1 > Designer: Refine the 'pre-View' action's enablement logic > --------------------------------------------------------- > > Key: TEIIDDES-368 > URL: https://jira.jboss.org/browse/TEIIDDES-368 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Mark Drilling > Assignee: Barry LaFond > Priority: Minor > Fix For: 7.1.1 > > > Internal request - refine the 'pre-view' action enablement logic. Only consider the sources that are actually used in the transformation to see if they have source bindings. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-516) cannot compile org.teiid.designer.ddl.importer: the import org.teiid.core.I18n cannot be resolved

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-516?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-516: ---------------------------------- Fix Version/s: 7.1 > cannot compile org.teiid.designer.ddl.importer: the import org.teiid.core.I18n cannot be resolved > ------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-516 > URL: https://jira.jboss.org/browse/TEIIDDES-516 > Project: Teiid Designer > Issue Type: Bug > Components: Build > Reporter: Nick Boldt > Assignee: John Verhaeg > Fix For: 7.1 > > > [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.9.0:compile (default-compile) on project org.teiid.designer.ddl.importer: Compilation failure: Compilation failure: > /mnt/hudson_workspace/workspace/jbosstools-teiid-designer/sources/plugins/org.teiid.designer.ddl.importer/src/org/teiid/designer/ddl/importer/DdlImporter.java (at line 34):[-1,-1] > import org.teiid.core.I18n; > ^^^^^^^^^^^^^^^^^^^ > The import org.teiid.core.I18n cannot be resolved > /mnt/hudson_workspace/workspace/jbosstools-teiid-designer/sources/plugins/org.teiid.designer.ddl.importer/src/org/teiid/designer/ddl/importer/DdlImporter.java (at line 35):[-1,-1] > import org.teiid.core.exception.EmptyArgumentException; > ^^^^^^^^^^^^^^^^^^^^^^^^ > The import org.teiid.core.exception cannot be resolved > /mnt/hudson_workspace/workspace/jbosstools-teiid-designer/sources/plugins/org.teiid.designer.ddl.importer/src/org/teiid/designer/ddl/importer/DdlImporter.java (at line 256):[-1,-1] > messages.add(I18n.format(DdlImporterI18n.ENTITY_NOT_FOUND_MSG, > ^^^^ > I18n cannot be resolved > http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-teiid-des... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-691) JBDS 4.0 beta1 - connecting successfully to a Teiid instance shows a red icon - until it is reconnected

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-691?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-691: ---------------------------------- Fix Version/s: 7.1.1 > JBDS 4.0 beta1 - connecting successfully to a Teiid instance shows a red icon - until it is reconnected > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-691 > URL: https://jira.jboss.org/browse/TEIIDDES-691 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.1, 7.1.1 > Environment: SOA-P 5.1 ER3 build > Version: 4.0.0.Beta1 > Build id: v201010052359R > Reporter: Len DiMaggio > Assignee: Barry LaFond > Fix For: 7.1.1 > > > If a connection is - successfully - made to a Teiid instance - the Teiid instance icon shows a red color - the red "x" is removed if the connection is reconnected. No errors are flagged or written to the .log -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-691) JBDS 4.0 beta1 - connecting successfully to a Teiid instance shows a red icon - until it is reconnected

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-691?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-691. ----------------------------------- Assignee: Barry LaFond Resolution: Done Fixed error icon problem for connected Teiid server. Also added methods to properly close Teiid instances (adminApi.close()) when servers are deleted to prevent stale sessions logging on server. Also added a simple server.ping in ServerManager.restoreState() so server is connected and Teiid View shows contents at start-up. > JBDS 4.0 beta1 - connecting successfully to a Teiid instance shows a red icon - until it is reconnected > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-691 > URL: https://jira.jboss.org/browse/TEIIDDES-691 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.1, 7.1.1 > Environment: SOA-P 5.1 ER3 build > Version: 4.0.0.Beta1 > Build id: v201010052359R > Reporter: Len DiMaggio > Assignee: Barry LaFond > > If a connection is - successfully - made to a Teiid instance - the Teiid instance icon shows a red color - the red "x" is removed if the connection is reconnected. No errors are flagged or written to the .log -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-672) Restore preferences defaults not 100% - transformation editor layout & miscellaneous, for example

by Paul Nittel (JIRA)

Restore preferences defaults not 100% - transformation editor layout & miscellaneous, for example ------------------------------------------------------------------------------------------------- Key: TEIIDDES-672 URL: https://jira.jboss.org/browse/TEIIDDES-672 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1.1 Environment: Windows, JBDS 4.0 Beta 1 Reporter: Paul Nittel Priority: Minor Fix For: 7.1.1 Windows > Preferences > Teiid Designer > Editor - Transformations tab. If I alter the SQL clauses and click the restore default button, the original values return. If I alter the values for Diagram Layout or Miscellaneous, clicking restore does not change these back to their original values. -- 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, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-673) Exported/Imported Teiid preferences does not capture all prefs

by Paul Nittel (JIRA)

Exported/Imported Teiid preferences does not capture all prefs -------------------------------------------------------------- Key: TEIIDDES-673 URL: https://jira.jboss.org/browse/TEIIDDES-673 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1.1 Environment: Windows, JBDS 4.0 Beta 1 Reporter: Paul Nittel Fix For: 7.1.1 I changed a number of Teiid Designer preferences (for example, both options under Preview Data are unchecked). Exported the prefs. Checked the boxes and imported the previously exported prefs. No change to the values. (For these check boxes, Restore Default works, however.) -- 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, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-693) Adding a Union to a transformation gets unhandled event loop exception (NPE)

by Paul Nittel (JIRA)

Adding a Union to a transformation gets unhandled event loop exception (NPE) ---------------------------------------------------------------------------- Key: TEIIDDES-693 URL: https://jira.jboss.org/browse/TEIIDDES-693 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.1.1 Environment: Windows, JBDS 4.0 Beta 1 Reporter: Paul Nittel I added a UNION of two AUTHORS tables to a transformation and got this: Error 2010-10-28 12:52:34.203 Unhandled event loop exception java.lang.NullPointerException at org.teiid.query.sql.lang.SetQuery.clone(SetQuery.java:172) at com.metamatrix.modeler.internal.transformation.util.TransformationSqlHelper.createSetQueryAddUnionSources(TransformationSqlHelper.java:795) at com.metamatrix.modeler.internal.transformation.util.TransformationSqlHelper.updateUnionSelectOnGroupsAdded(TransformationSqlHelper.java:392) at com.metamatrix.modeler.transformation.ui.actions.TransformationSourceManager.addUnionSources(TransformationSourceManager.java:585) at com.metamatrix.modeler.transformation.ui.actions.AddUnionSourceAction.doRun(AddUnionSourceAction.java:136) at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:537) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:540) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-692) Undo Clear Transformation gets Index Out of Bound exception

by Paul Nittel (JIRA)

Undo Clear Transformation gets Index Out of Bound exception ----------------------------------------------------------- Key: TEIIDDES-692 URL: https://jira.jboss.org/browse/TEIIDDES-692 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1.1 Environment: Windows, JBDS 4.0 Beta 1 Reporter: Paul Nittel Fix For: 7.1.1 If a transformation is cleared, undo-ing the clear operation fails with an index out of bounds exception. Error 2010-10-28 12:28:55.390 Error processing Undo: Clear Transformation org.eclipse.emf.common.util.AbstractEList$BasicIndexOutOfBoundsException: index=1, size=0 at org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java:338) at org.eclipse.emf.edit.command.RemoveCommand.doUndo(RemoveCommand.java:471) at org.eclipse.emf.edit.command.AbstractOverrideableCommand.undo(AbstractOverrideableCommand.java:162) at org.eclipse.emf.common.command.CompoundCommand.undo(CompoundCommand.java:333) at com.metamatrix.modeler.internal.core.transaction.UndoableImpl.undo(UndoableImpl.java:75) at com.metamatrix.modeler.internal.ui.undo.ModelerUndoManager.undo(ModelerUndoManager.java:306) at com.metamatrix.modeler.internal.ui.actions.UndoAction.performAction(UndoAction.java:49) at com.metamatrix.modeler.internal.ui.actions.AbstractUndoRedoAction$1.run(AbstractUndoRedoAction.java:84) at org.eclipse.ui.actions.WorkspaceModifyDelegatingOperation.execute(WorkspaceModifyDelegatingOperation.java:69) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at com.metamatrix.modeler.internal.ui.actions.AbstractUndoRedoAction.doRun(AbstractUndoRedoAction.java:97) at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:537) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:540) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:230) 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: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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-629) When creating a UDF, the Invocation class and method should be optional

by Van Halbert (JIRA)

When creating a UDF, the Invocation class and method should be optional ----------------------------------------------------------------------- Key: TEIIDDES-629 URL: https://jira.jboss.org/browse/TEIIDDES-629 Project: Teiid Designer Issue Type: Bug Components: Editors Reporter: Van Halbert According to Teiid Developer Guide, the Invocation Class and Method are optional properties, because in the cases where the function is REQUIRED to be a push down, it will never be called by the engine. Also, it would be nice for the Category, to present the list of current categories that have been defined just so you can select an already defined one (this just keeps user typing errors to minimal) or let the user override and add a new one if one if needed. -- 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, 1 month

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2010