July 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-958) Provide a way for the user to see the Teiid SQL Grammer reserved words

by Van Halbert (JIRA)

Provide a way for the user to see the Teiid SQL Grammer reserved words ---------------------------------------------------------------------- Key: TEIIDDES-958 URL: https://issues.jboss.org/browse/TEIIDDES-958 Project: Teiid Designer Issue Type: Enhancement Components: Modeling, Validation Affects Versions: 7.3 Reporter: Van Halbert Provide a way for the user to view the Teiid grammer reserved words. It would nice to know/see these whenever procedure language constructs can be built. The constants are currently stored here: SQLConstants.java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-776) Data Roles: After unchecking a model, cannot check subordinate metadata, like columns

by Paul Nittel (JIRA)

Data Roles: After unchecking a model, cannot check subordinate metadata, like columns ------------------------------------------------------------------------------------- Key: TEIIDDES-776 URL: https://issues.jboss.org/browse/TEIIDDES-776 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1.1 Reporter: Paul Nittel In the case where an administrator wishes to prevent access to all columns but a relatively few, they should be able to: Uncheck the model (which causes all subordinate objects to be unchecked) Check the small number to which access is desired. What happens is once the model is unchecked, the subordinate objects cannot be checked. (Also, if all subordinate objects are manually unchecked, the model has a grayed-out check as if there is a checked subordinate object. If all objects under a model are unchecked, the model itself should also be unchecked.) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1005) Getting exception when attempting to do a metadata search in Designer

by Mark Drilling (JIRA)

Getting exception when attempting to do a metadata search in Designer --------------------------------------------------------------------- Key: TEIIDDES-1005 URL: https://issues.jboss.org/browse/TEIIDDES-1005 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.1.1 Environment: Fedora 14, x64 JDBS 4.0.1 Reporter: Mark Drilling Assignee: Mark Drilling I'm getting exceptions when attempting a metadata search - after I've imported and rebuilt a model project in Designer. To reproduce: 1) Import the attached SearchProject.zip into Designer (Import... > General > Existing Projects into Workspace 2) After import the project has (for me) 27 errors. To correct the errors, 1) close project, 2) open project, 3) rebuild project. Then the project is error free. 3) Attempt a metadata search. (Search > Teiid Designer > Metadata...) The search attempt results in the attached stack trace. 4) Either a) Close JBDS and Restart or b) delete the offending VDB from #3 will clear things up and eliminate the exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
5
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] Debbie Steigner commented on TEIIDDES-1009: ------------------------------------------- When the customer ran a relational table import, it succeeds but the below error is written to the .log file: !ENTRY org.eclipse.ui 4 0 2011-07-29 15:31:35.990 !MESSAGE Unhandled event loop exception !STACK 0 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:468) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340) at org.eclipse.swt.widgets.Text.setText(Text.java:1950) at com.metamatrix.modeler.internal.relational.ui.wizards.ImportRelationalTablesMainPage.setObjectLocation(ImportRelationalTablesMainPage.java:483) at com.metamatrix.modeler.internal.relational.ui.wizards.ImportRelationalTablesMainPage.handleModelFolderBrowseButtonPressed(ImportRelationalTablesMainPage.java:457) at com.metamatrix.modeler.internal.relational.ui.wizards.ImportRelationalTablesMainPage.handleEvent(ImportRelationalTablesMainPage.java:150) 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.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:147) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) 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: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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) > Improve Designer "Metadata from Text files on file system" import option > ------------------------------------------------------------------------ > > Key: TEIIDDES-1009 > URL: https://issues.jboss.org/browse/TEIIDDES-1009 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: eds > > Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. > Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1003) Re-Import of Model Project Set leaves project with multiple errors

by Mark Drilling (JIRA)

Re-Import of Model Project Set leaves project with multiple errors ------------------------------------------------------------------ Key: TEIIDDES-1003 URL: https://issues.jboss.org/browse/TEIIDDES-1003 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1.1 Environment: JBDS 4.0.1, Fedora 14, 64bit Reporter: Mark Drilling Assignee: Mark Drilling I've exported an error-free project as a Model Project Set (attached). I then delete the original project, then re-import the project set via (Import... > General > Existing Projects into Workspace). Upon import, the project has 27 errors. The model "AllCustomerAccounts" appears to be corrupted. If I (1) close project, (2) reopen project, (3) rebuild project the errors are resolved. This may be OS-specific, Barry could not reproduce with same version of JBDS on a different 32bit Ubuntu linux. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1018) Allow User to Override Default Web Service Timeouts When Generating JBossWS-CXF WAR

by Ted Jones (JIRA)

Allow User to Override Default Web Service Timeouts When Generating JBossWS-CXF WAR ----------------------------------------------------------------------------------- Key: TEIIDDES-1018 URL: https://issues.jboss.org/browse/TEIIDDES-1018 Project: Teiid Designer Issue Type: Enhancement Components: Web Services Support Reporter: Ted Jones Assignee: Ted Jones Need to provide a way for the user to override the timeout value for web services so that the war is generated with the overidden values -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-843) Teiid "Build XML Documents from XML Schema" dialog is too wide

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-843?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-843: ------------------------------------- Assignee: Barry LaFond (was: Dan Florian) > Teiid "Build XML Documents from XML Schema" dialog is too wide > -------------------------------------------------------------- > > Key: TEIIDDES-843 > URL: https://issues.jboss.org/browse/TEIIDDES-843 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 7.2 > Environment: Linux, GTK, x86 > Java 6 Open JDK > Reporter: Denis Golovin > Assignee: Barry LaFond > Priority: Minor > Labels: usability > Fix For: 7.5 > > Attachments: screenshot100.png > > > See attached [^screenshot100.png] which size is about 1900x900. > Possible solutions are: > 1. list with checkboxes and move sorting to the next step which would be mandatory if "Keep sorted alphabetically" is unselected. > 2. Use tabs to separate selecting from ordering > 3. Put ordering list under selecting list -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-812) DDL Export XSLT files need to be upgraded/improved

by Barry LaFond (JIRA)

DDL Export XSLT files need to be upgraded/improved -------------------------------------------------- Key: TEIIDDES-812 URL: https://issues.jboss.org/browse/TEIIDDES-812 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.2, 7.1.1, 7.3 Reporter: Barry LaFond Priority: Critical Fix For: 7.4 After working import issue TEIIDDES-215, it's become apparent that our XSLT's for various DB's need to be revisited. For instance, there is no logic in PostgreSQL version to check for integer types that have AUTOINCREMENT == TRUE. These should be exported as SERIAL datatypes. Same for BIGSERIAL. There is other missing logic. We need to: 1) Create a doc or series of docs describing what datatype conversions should be done on IMPORT JDBC and EXPORT DDL 2) Create sub-tasks for implementing these docs for all DB's 3) Possibly create extension point(s) to handle "new" DB types more effeciently -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1014) java.lang.NullPointerException in Manage Extended Prioperties" Dialog After Removing a Property

by Ted Jones (JIRA)

java.lang.NullPointerException in Manage Extended Prioperties" Dialog After Removing a Property ----------------------------------------------------------------------------------------------- Key: TEIIDDES-1014 URL: https://issues.jboss.org/browse/TEIIDDES-1014 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.4 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.5, 7.4 After adding a few rows, removing a row and clicking on one of the remaining rows, a java.lang.NullPointerException is encountered. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1009: ----------------------------------- Summary: Improve Designer "Metadata from Text files on file system" import option (was: Teiid Designer "Import Metadata from Text files on file system" should allow for all metadata to be imported) > Improve Designer "Metadata from Text files on file system" import option > ------------------------------------------------------------------------ > > Key: TEIIDDES-1009 > URL: https://issues.jboss.org/browse/TEIIDDES-1009 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: eds > > Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2011