June 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-191) XSD as Relational importer has problems with child elements with many parents

by Greg Haber (JIRA)

XSD as Relational importer has problems with child elements with many parents ----------------------------------------------------------------------------- Key: TEIIDDES-191 URL: https://jira.jboss.org/jira/browse/TEIIDDES-191 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: Teiid Designer 6.0.0 official (14 May 2009) release Reporter: Greg Haber Attachments: address.xsd, person.xsd, person2.xml, person2.xsd I've encountered a lot of problems with the Teiid Designer XML as Relational Importer (and with its legacy ancestor) dealing with importing XSDs where a child element has multiple parents. The importer currently treats all elements throughout the XSD that have the same name and type as the same, and so models that element(s) as a single table with multiple parents, if the number of parents is above a configurable number (currently defaults to 3). Which is all well and good in theory, but in practice it seems to hit a number of problems 1) During the import process, if the selection of document root elements is left at the default, not all needed tables are generated. See person.xsd example attached. 2) If all possible root elements are selected, it looks mostly right, but there are often extra elements in the child tables (again try with person.xsd). Plus, the tables don't actually work at runtime correctly (try using attached person2.xml as the data source - notice that you can only get to the spouse's father from Person, not to their own father). I've also attached some other example problem XSDs - person2.xsd, and address.xsd Now, in some cases a reasonable workaround is to up the number of allowed parents parameter, so that everything gets folded into a single table. But that isn't a general solution, as it doesn't work with things like person2.xsd. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-695) Cannot paste into Table Editor cell via CTRL-V - get error msg and NPE

by Paul Nittel (JIRA)

Cannot paste into Table Editor cell via CTRL-V - get error msg and NPE ---------------------------------------------------------------------- Key: TEIIDDES-695 URL: https://jira.jboss.org/browse/TEIIDDES-695 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 I tried to paste a value into a table editor column by CTRL-V and get an error and exception. I _am_ able to paste via right-click > Paste. (I used a relational source model/Columns tab.) Error 2010-10-29 09:53:53.453 Cannot set value "w00t" for the name property of this Column java.lang.NullPointerException at org.eclipse.emf.edit.provider.ItemProviderAdapter.getPropertyDescriptor(ItemProviderAdapter.java:258) at com.metamatrix.modeler.internal.ui.properties.ModelObjectPropertySource.getPropertyValue(ModelObjectPropertySource.java:332) at com.metamatrix.modeler.internal.ui.table.ModelRowElement.setValue(ModelRowElement.java:244) at com.metamatrix.modeler.internal.ui.table.ModelTableEditor.pasteClipboardContents(ModelTableEditor.java:1400) at com.metamatrix.modeler.internal.ui.actions.TableClipboardPasteAction.doRun(TableClipboardPasteAction.java:41) 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.commands.ActionHandler.execute(ActionHandler.java:119) 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.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1253) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1103) at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1427) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1099) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1508) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4268) at org.eclipse.swt.widgets.Text.WM_CHAR(Text.java:2175) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4160) at org.eclipse.swt.widgets.Text.windowProc(Text.java:2170) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4873) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2459) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655) 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

12 years, 5 months

3
6
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

12 years, 6 months

4
4
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

12 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-985) Create Test script to exercise Teiid Designer Search wizards

by Barry LaFond (JIRA)

Create Test script to exercise Teiid Designer Search wizards ------------------------------------------------------------ Key: TEIIDDES-985 URL: https://issues.jboss.org/browse/TEIIDDES-985 Project: Teiid Designer Issue Type: Sub-task Components: Documentation, Testing Affects Versions: 7.5 Reporter: Barry LaFond Priority: Critical Fix For: 7.5 Teiid Designer has 4 "Search > Teiid Designer" wizard contributions. Write a test script to exercise all 4 wizards and include a Model Project Set that represents a large enough data set to test full or new full functionality for these features. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-905) Replace EMF-based Model Extensions with new framework

by Barry LaFond (JIRA)

Replace EMF-based Model Extensions with new framework ----------------------------------------------------- Key: TEIIDDES-905 URL: https://issues.jboss.org/browse/TEIIDDES-905 Project: Teiid Designer Issue Type: Enhancement Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.4 Designer's current Model Extensions framework has some limitations which include: 1. The current framework allows for only 1 extension model. 2. Extension models are included as a dependent models in VDBs. 3. When sequenced through publishing into the Modeshape repository none of the default "extended" property values are currently sequenced. There is no mechanism in Modeshape to associate 2 or more documents in this way. 4. When using the EMF Extension Model, EMF controls when Annotation objects are created, and we're creating annotation objects even when none are strictly needed (e.g., all the tags in the annotation have default values, and thus don't appear in the XMI file). The result is a lot of unnecessary Annotation objects. Need to design a new framework that is scalable, allows for applying multiple extensions, includes the extension metadata within a model (initial values and types) and can be easily adapted/sequenced by Modeshape. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (TEIIDDES-993) Add package diagram for webservices that shows the relationships between the different artifacts

by Van Halbert (JIRA)

Add package diagram for webservices that shows the relationships between the different artifacts ------------------------------------------------------------------------------------------------ Key: TEIIDDES-993 URL: https://issues.jboss.org/browse/TEIIDDES-993 Project: Teiid Designer Issue Type: Enhancement Components: Diagrams Affects Versions: 7.5 Reporter: Van Halbert For webservices, provide a package diagram that shows what the relationships are for a given webservice. This would be very useful to help visualize all the parts and their relationship to creating the webservice. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-620) Add Option for Embedded Teiid Connection vs JNDI in WAR Generation

by Ted Jones (JIRA)

Add Option for Embedded Teiid Connection vs JNDI in WAR Generation ------------------------------------------------------------------ Key: TEIIDDES-620 URL: https://jira.jboss.org/browse/TEIIDDES-620 Project: Teiid Designer Issue Type: Feature Request Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 Need to allow for a embedded Teiid connection in the war generation process in addition to the current JNDI connection. This is required for HTTPBasic support. -- 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

12 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-992) Allow the use of pushdown functions without requiring Java programming

by Bernd Groh (JIRA)

Allow the use of pushdown functions without requiring Java programming ---------------------------------------------------------------------- Key: TEIIDDES-992 URL: https://issues.jboss.org/browse/TEIIDDES-992 Project: Teiid Designer Issue Type: Feature Request Reporter: Bernd Groh Currently, in order to use a database function, even if pushdown is required, it is still necessary to add the function interface to a Java class within the connector, and the connector then must be deployed to the server in order to allow for this pushdown function to be used within the Designer. This creates a lot of extra effort every time you want to make use of a new database function. Particularly, given the schema designer doesn't necessarily have access to either the connector code or the server, and then must involve other parties simply to be able to use an additional database function. It would be very beneficial to speedy schema development if that was not necessary, and if, say, the interface could be defined on the Designer side, added to the VDB, and then deployed as part of the VDB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
47
0 / 0

[JBoss JIRA] Created: (TEIIDDES-936) Version 7.5 Release Work

by Barry LaFond (JIRA)

Version 7.5 Release Work ------------------------ Key: TEIIDDES-936 URL: https://issues.jboss.org/browse/TEIIDDES-936 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 7.5 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.5 All general work related to releasing 7.5 Starts with upgrading Trunk feature.xml, MANIFEST.MF and pom.xml files to 7.5 qualifier -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2011