November 2011 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-57) XSD Import brings dependency when it's already in workspace

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-57?page=com.atlassian.jira.plugi... ] Barry LaFond resolved TEIIDDES-57. ---------------------------------- Assignee: Barry LaFond Resolution: Won't Fix The importer does have a "overwrite if exists" option which prevents duplicate XSD files. Also, if user has not selected a target project/folder when wizard is launched, the "target location/folder" won't be selected, so we don't know where to check for duplicate/existing XSD's until this location is set. Marking as Won't fix > XSD Import brings dependency when it's already in workspace > ----------------------------------------------------------- > > Key: TEIIDDES-57 > URL: https://issues.jboss.org/browse/TEIIDDES-57 > Project: Teiid Designer > Issue Type: Task > Components: Import/Export > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: Future > > Attachments: DependencyQuestion.jpg > > > I had BookDatatypes.xsd in my workspace when I imported books.xsd. The dialog requesting to bring along the dependent xsd was displayed, but should not have been: it's already in my workspace. Screenshot attached. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-950) In the Create Data Source dialog, it would be good to indicate that the Data Source Name is also the JNDI name, so that the user can connect the dots with this common term

by Van Halbert (JIRA)

In the Create Data Source dialog, it would be good to indicate that the Data Source Name is also the JNDI name, so that the user can connect the dots with this common term --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-950 URL: https://issues.jboss.org/browse/TEIIDDES-950 Project: Teiid Designer Issue Type: Enhancement Components: Dialogs Affects Versions: 7.1.1 Reporter: Van Halbert Priority: Minor In the Create Data Source dialog, it would be good to indicate that the Data Source Name is also the JNDI name, so that the user can connect the dots with this common term -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

4
4
0 / 0

[JBoss JIRA] (TEIIDDES-1054) RFE in Teiid Designer for an Unselect all button when updating Source Models

by Barry LaFond (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1054?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1054. ------------------------------------ Resolution: Done Tweaked UI components for difference & compare panels. Replaced sashform with group, removed splitter. Added select/unselect all buttons to toolbar to save space. > RFE in Teiid Designer for an Unselect all button when updating Source Models > ---------------------------------------------------------------------------- > > Key: TEIIDDES-1054 > URL: https://issues.jboss.org/browse/TEIIDDES-1054 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.1.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 7.6 > > > When updating a source model, on the dialog which shows you the differences between the original and updated model (new/old/unchanged). > By default all the items are checked, meaning the source model will be updated to only what has been selected in the previous screen. > Most of the time we want to *add* tables to our source model. This means we need to unselect every item in the differences dialog except the ones we just selected. > There's no deselect all button, which we would like, so we don't have to deselect every checkbox one by one (especially when we have hundreds of tables in a model). > These checkbox items are the children of a checkbox for the schema, so typically in a UI like this you would expect unselecting the parent checkbox to unselect all its children also. This doesn't happen. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1027) CLONE - Allow for the parsing of fixed width files that don't use delimiters.

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1027?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-1027: ------------------------------------- Assignee: (was: Steven Hawkins) > CLONE - Allow for the parsing of fixed width files that don't use delimiters. > ----------------------------------------------------------------------------- > > Key: TEIIDDES-1027 > URL: https://issues.jboss.org/browse/TEIIDDES-1027 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.6 > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.7 > > > Parsing a fixed width file that does not use a delimiter, or uses a newline for wrapping, is not currently possible. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-988) Convert The ModelExplorerResourceNavigator To Use Eclipse's Common Navigator Framework

by Dan Florian (JIRA)

Convert The ModelExplorerResourceNavigator To Use Eclipse's Common Navigator Framework -------------------------------------------------------------------------------------- Key: TEIIDDES-988 URL: https://issues.jboss.org/browse/TEIIDDES-988 Project: Teiid Designer Issue Type: Task Affects Versions: 7.4 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.5 The ModelExplorerResourceNavigator uses the deprecated framework of the ResourceNavigator and should be rewritten using the CNF (Common Navigator Framework). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
5
0 / 0

[JBoss JIRA] (TEIIDDES-1117) XML Schema importer sez "No XSD resources selected for import", but it meant to say "Select Target Project or Folder"

by Paul Nittel (Created) (JIRA)

XML Schema importer sez "No XSD resources selected for import", but it meant to say "Select Target Project or Folder" --------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1117 URL: https://issues.jboss.org/browse/TEIIDDES-1117 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4.2 Environment: JBDS 4.1.1CR1 H1067 Reporter: Paul Nittel Priority: Minor Attachments: XsdResourceWasSelected_honest.png I selected File > Import > XML Schemas The XSD is on the file system. After selecting the XSD I wanted to import, the error message indicated I needed to select the XSD. Once I'd filled in the project into which I was importing, the error cleared. (See the screenshot). The error message should be corrected to truly indicate the state of the wizard. -- 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

14 years, 5 months

5
4
0 / 0

[JBoss JIRA] (TEIIDDES-1121) NPE during the WSDL import

by Ramesh Reddy (Created) (JIRA)

NPE during the WSDL import -------------------------- Key: TEIIDDES-1121 URL: https://issues.jboss.org/browse/TEIIDDES-1121 Project: Teiid Designer Issue Type: Bug Reporter: Ramesh Reddy Attachments: hello_world.wsdl While importing the attached WSDL as source model, the following NPE thrown and operation did not complete. If only selected one of the operation then it created fine. java.lang.NullPointerException at com.metamatrix.modeler.modelgenerator.wsdl.ui.internal.wizards.SelectWsdlOperationsPage.addOperationDetails(SelectWsdlOperationsPage.java:293) at com.metamatrix.modeler.modelgenerator.wsdl.ui.internal.wizards.SelectWsdlOperationsPage.updateSelectionDetailsArea(SelectWsdlOperationsPage.java:271) at com.metamatrix.modeler.modelgenerator.wsdl.ui.internal.wizards.SelectWsdlOperationsPage.updateTreeSelectionDetails(SelectWsdlOperationsPage.java:149) at com.metamatrix.modeler.modelgenerator.wsdl.ui.internal.wizards.SelectWsdlOperationsPage.handleEvent(SelectWsdlOperationsPage.java:126) 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:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:150) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:277) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171) at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:97) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) 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:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- 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

14 years, 5 months

5
4
0 / 0

[JBoss JIRA] (TEIIDDES-1119) Need for global workspace location

by Barry LaFond (Created) (JIRA)

Need for global workspace location ---------------------------------- Key: TEIIDDES-1119 URL: https://issues.jboss.org/browse/TEIIDDES-1119 Project: Teiid Designer Issue Type: Feature Request Components: Eclipse Integration Reporter: Barry LaFond Assignee: Barry LaFond With 7.6 Teiid Designer will be managing a new Model Extension framework which allows users to define Model Extension Definitions (MEDs) to inject additional properties into relational, web services, XML document and function models. Initial design is to maintain a registry or both built-in and user-defined MED's within the user's workspace/.metadata/org.teiid.designer.extension folder. Designer is also maintaining a similar Teiid Server registry in workspace/.metadata/org.teiid.designer.dqp The "Import VDB" feature will probably need a place to store a registry of "Translator Overrides" so user can re-use these across VDB's rather than re-inputing these properties manually each time in their VDB editors. The Data Tools Connection profile registry is also stored in a workspace/.metadata/org.eclipse.datatools.connectivity folder. Data Tool provides input/export features for persisting portions or all of the profile registry across workspace, but requires user to import/export each time. Eclipse's ".metadata" folder concept is good from a single workspace standpoint, but these registries are: 1) at risk of being deleted if workspace is cleared 2) registry data (i.e. files) are not available/exposed for proper version control So a solution might be to create the concept of a Global Workspace Location. This location would be set by the user if they choose. This location would contain folders for Teiid Server, Model Extension, Translator Overrides, Connection Profiles such that if a user changes workspaces they wouldn't necessarily have to re-import all of this data. Maybe provide a "Global Workspace Explorer" view that would have some features/actions to do some appropriate management of the artifacts. This would be a Usability -- 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

14 years, 5 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB

by Barry LaFond (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1118: ----------------------------------- Fix Version/s: 7.7 Assignee: Dan Florian (was: Barry LaFond) > 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: Dan Florian > Fix For: 7.7 > > > 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1101) Datatype Resolver Dialog sizing may hide buttons

by Paul Nittel (Created) (JIRA)

Datatype Resolver Dialog sizing may hide buttons ------------------------------------------------ Key: TEIIDDES-1101 URL: https://issues.jboss.org/browse/TEIIDDES-1101 Project: Teiid Designer Issue Type: Bug Components: Dialogs Environment: RHEL6-32 JBDS 4.1.1 M2 Reporter: Paul Nittel Priority: Minor I'm running the Designer in an admittedly small window (virtual machine in my case, but it could just be a laptop thing). When the type resolver first displays, the buttons to convert the SQL Symbol are hidden. There is a vertical scroll bar, but when scrolled to the bottom, the buttons are only slightly revealed. If we could ensure the buttons would be completely visible by either scrolling or resizing the bottom section of the dialog (can't; it's all fixed), it would make for a better user experience. Screenshot attached. -- 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

14 years, 5 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2011