January 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-764) VDB Editor Usability - when sync'ing it should also perform save

by Van Halbert (JIRA)

VDB Editor Usability - when sync'ing it should also perform save ---------------------------------------------------------------- Key: TEIIDDES-764 URL: https://issues.jboss.org/browse/TEIIDDES-764 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 7.1.1, 7.2 Reporter: Van Halbert Priority: Minor >From a usability stand point, it would be good when performing synchronization of models that the vdb could also be saved. The combination of these 2 steps will be used heavily, and it would be nice to make it a single step. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-740) Adding physical tables to a transformation with "Modeling->Add to From Clause" only works once.

by John Doyle (JIRA)

Adding physical tables to a transformation with "Modeling->Add to From Clause" only works once. ----------------------------------------------------------------------------------------------- Key: TEIIDDES-740 URL: https://issues.jboss.org/browse/TEIIDDES-740 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Environment: JBDS Beta2 Reporter: John Doyle Adding a physical table to a transformation by right-clicking on the physical table in the Model Explorer and selecting Modeling->Add to From Clause works when there is no physical model in the transformation. If one is already there, you can click, but nothing happens. Once you remove the existing table, it works again. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-772) When closing a project with a VDB open in its editor, you may get Unhandled Event Loop Exception

by Paul Nittel (JIRA)

When closing a project with a VDB open in its editor, you may get Unhandled Event Loop Exception ------------------------------------------------------------------------------------------------ Key: TEIIDDES-772 URL: https://issues.jboss.org/browse/TEIIDDES-772 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1.1 Environment: Used a version of Designer supplied by Barry last week Reporter: Paul Nittel Attachments: TTT_UELE_MPS.zip I opened a project, created a VDB, saved the VDB, then closed the project. I got this: Error 2011-01-06 11:26:09.146 Unhandled event loop exception org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) Caused by: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.widgets.Widget.error(Widget.java:466) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:403) at org.eclipse.swt.widgets.Table.deselectAll(Table.java:956) at org.eclipse.jface.viewers.TableViewer.doDeselectAll(TableViewer.java:277) at org.eclipse.jface.viewers.AbstractTableViewer.setSelectionToWidget(AbstractTableViewer.java:908) at org.eclipse.jface.viewers.StructuredViewer.setSelectionToWidget(StructuredViewer.java:1741) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1429) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1383) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1485) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1444) at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor.vdbNotification(VdbEditor.java:974) at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$27$1.run(VdbEditor.java:920) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 22 more I'll attach the model project set. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-771) DB2, Sybase & SQL Server Import Model Processor contributions have wrong driver class names in plugin.xml

by Van Halbert (JIRA)

DB2, Sybase & SQL Server Import Model Processor contributions have wrong driver class names in plugin.xml --------------------------------------------------------------------------------------------------------- Key: TEIIDDES-771 URL: https://issues.jboss.org/browse/TEIIDDES-771 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.3, 7.0, 7.1 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.1.1 DB2, Sybase & SQL Server Import Model Processor contributions have wrong driver class names in plugin.xml. They still contain "com.metamatrix.xxxx.xxDriver" entries which no longer exist. Need to replace with valid driver class names. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-731) Support for Sybase missing in Teiid designer export dialog

by Boris Belovic (JIRA)

Support for Sybase missing in Teiid designer export dialog ---------------------------------------------------------- Key: TEIIDDES-731 URL: https://jira.jboss.org/browse/TEIIDDES-731 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1 Reporter: Boris Belovic Priority: Blocker Support for Sybase is missing in Teiid designer. I noticed this when I was generating DDL scripts for materialized views. There is no option for Sybase, so the designer can't create DDL scripts for externally materialized table on Sybase DB. SOA-P 5.1 will ship with support for Sybase 15.0.2. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-741) Execute VDB Action does not always set the correct VDB name in the VDB name property.

by John Doyle (JIRA)

Execute VDB Action does not always set the correct VDB name in the VDB name property. ------------------------------------------------------------------------------------- Key: TEIIDDES-741 URL: https://issues.jboss.org/browse/TEIIDDES-741 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1.1 Environment: JBDS Beta 2 Reporter: John Doyle Assignee: John Doyle Priority: Blocker Fix For: 7.1.1 I haven't figured out why, but sometimes the Execute VDB action comes up with the right VDB name, and sometimes it comes up with the wrong name, and existing VDB, but not the one you're trying to execute. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-773) Preview will fail quietly if the JDBC connection is not sucessfully created.

by John Doyle (JIRA)

Preview will fail quietly if the JDBC connection is not sucessfully created. ---------------------------------------------------------------------------- Key: TEIIDDES-773 URL: https://issues.jboss.org/browse/TEIIDDES-773 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1.1, 7.2 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1.1, 7.2 I first noted this in the case where you do not supply a JDBC password in Designer's Teiid confguration. Initially I considered this invalid, Teiid can be configured this way if a user desires. Because of this we can't consider JDBC credentials with no password invalid. We should however notify the user helpfully if a connection fails. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-749) Creation of a new Teiid instance in the JBDS Teiid Designer should prompt the user to make that the default

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-749?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-749: ---------------------------------- Assignee: Barry LaFond Fix Version/s: 7.1.1 (was: 7.3) > Creation of a new Teiid instance in the JBDS Teiid Designer should prompt the user to make that the default > ----------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-749 > URL: https://issues.jboss.org/browse/TEIIDDES-749 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview, VDB & Execution > Affects Versions: 7.1.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 7.1.1 > > > When you create a new Teiid instance, and one already existed, the user should be prompted if they want this new instance to be the default since many of the other actions automatically use the default server without giving the user a chance to explicitly select one. The alternative, of course, would be to change all of the other actions to allow an explicit selection. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-749) Creation of a new Teiid instance in the JBDS Teiid Designer should prompt the user to make that the default

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-749?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-749. ----------------------------------- Resolution: Done This was completed as part of TEIIDDES-755. Marking as done. > Creation of a new Teiid instance in the JBDS Teiid Designer should prompt the user to make that the default > ----------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-749 > URL: https://issues.jboss.org/browse/TEIIDDES-749 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview, VDB & Execution > Affects Versions: 7.1.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 7.1.1 > > > When you create a new Teiid instance, and one already existed, the user should be prompted if they want this new instance to be the default since many of the other actions automatically use the default server without giving the user a chance to explicitly select one. The alternative, of course, would be to change all of the other actions to allow an explicit selection. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-503) Update Designer embedded help to reflect 7.0 changes

by Barry LaFond (JIRA)

Update Designer embedded help to reflect 7.0 changes ---------------------------------------------------- Key: TEIIDDES-503 URL: https://jira.jboss.org/browse/TEIIDDES-503 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0, 7.1 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.1 Changes to the VDB editor, Connections (JCA & DTP) and the adoption of the new "Teiid in AS" concept requires updating Designer's embedded help. -- 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

14 years, 11 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2011