December 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-116) Add ability to perform partial copy model operations in new model wizard

by Barry LaFond (JIRA)

Add ability to perform partial copy model operations in new model wizard ------------------------------------------------------------------------ Key: TEIIDDES-116 URL: https://jira.jboss.org/jira/browse/TEIIDDES-116 Project: Teiid Designer Issue Type: Sub-task Components: Modeling Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: 6.1.0 -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-474) Extension Module attribute with name in camel case is shown as multiple words

by Paul Nittel (JIRA)

Extension Module attribute with name in camel case is shown as multiple words ----------------------------------------------------------------------------- Key: TEIIDDES-474 URL: https://jira.jboss.org/browse/TEIIDDES-474 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: Designer 7.0.0 built 6/18/2010 Reporter: Paul Nittel I created an extension module, within that an extension package containing an XClass for a relational column, and, finally, with a single attribute: ShoeSize (an EInt). I associated this extension with a relational model (Parts) and viewed the PARTS.PARTS_ID column. There, I found, under Extensions, the attribute "Shoe Size"--with a space between "Shoe" and "Size". I don't know what ramifications might lie down the road, but it's definitely not the way it was input. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-553) Finish adding the "Name:Type" capability to procedures and the new Function model type

by Paul Nittel (JIRA)

Finish adding the "Name:Type" capability to procedures and the new Function model type -------------------------------------------------------------------------------------- Key: TEIIDDES-553 URL: https://jira.jboss.org/browse/TEIIDDES-553 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.1 Environment: All Reporter: Paul Nittel When I'm modeling new relational models and creating columns, I can type the name of the column like "CoolColumnName:string(10)" and I not only get the column, I also get that its a String with a length of 10 characters. If I do that to a new Function model I get a column with the awkward name of "CoolColumnName:string(10)". Not valid! Please extend this valuable capability to other model type where applicable. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-552) Function model should be automatically added to the VDB when a referencing model is added

by Paul Nittel (JIRA)

Function model should be automatically added to the VDB when a referencing model is added ----------------------------------------------------------------------------------------- Key: TEIIDDES-552 URL: https://jira.jboss.org/browse/TEIIDDES-552 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Just like we automatically add XML Schema Documents (XSD) to a VDB when an XML document model is added, so should the function model when a referencing model is added. This will greatly increase the chance of first-time success! -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-477) Relationship Navigator view Focus pull-down is incorrectly sized

by Paul Nittel (JIRA)

Relationship Navigator view Focus pull-down is incorrectly sized ---------------------------------------------------------------- Key: TEIIDDES-477 URL: https://jira.jboss.org/browse/TEIIDDES-477 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 7.0 Environment: Teiid Designer 7.0.0 running in JBDS 3.0.1 Reporter: Paul Nittel While playing in the Relationship world, I noticed the Focus pulldown in the Relationship Navigator view is too small to see anything, and does not resize, even when the view is maximized in Eclipse. See attached screenshot. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-676) Add good defaults to XML Schema Import Wizard

by John Verhaeg (JIRA)

Add good defaults to XML Schema Import Wizard --------------------------------------------- Key: TEIIDDES-676 URL: https://jira.jboss.org/browse/TEIIDDES-676 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.1 Reporter: John Verhaeg We should choose good defaults throughout this wizard, such as: - Pre-select the "from file system" option (vs. "via URL") on the first page - Auto-populate the "From directory" field to the user folder and remember whatever the user finally chooses thereafter. Working with a selection dialog that only allows you to choose a folder is too different from the norm to not be awkward. Always takes me a few seconds to remember why the *file* I'm trying to select is grayed-out. - Auto-populate the "Into folder" field if there is only one folder, a single project folder, in the workspace. - Provide a way to create a project so the user doesn't have to exit the entire wizard if they forget to first do that. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-652) Rose importer fails with multiple exceptions

by Paul Nittel (JIRA)

Rose importer fails with multiple exceptions -------------------------------------------- Key: TEIIDDES-652 URL: https://jira.jboss.org/browse/TEIIDDES-652 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1.1 Environment: JBDS H30 Reporter: Paul Nittel Fix For: 7.1.1 Attachments: NestedClass.mdl I used the Rose importer to import the attached .mdl file. I checked all objects as I progressed through the wizard. Eventually I received: Error 2010-10-06 10:26:05.71 java.lang.UnsupportedOperationException at org.eclipse.uml2.common.util.DerivedEObjectEList$DerivedListIterator.add(DerivedEObjectEList.java:278) at java.util.AbstractSequentialList.add(AbstractSequentialList.java:129) at org.eclipse.uml2.common.util.DerivedEObjectEList.addUnique(DerivedEObjectEList.java:636) at org.eclipse.uml2.common.util.DerivedEObjectEList.add(DerivedEObjectEList.java:623) at java.util.AbstractList.add(AbstractList.java:91) at com.metamatrix.rose.internal.handler.UmlHandler.createClass(UmlHandler.java:589) at com.metamatrix.rose.internal.handler.AbstractRoseHandler.visitObject(AbstractRoseHandler.java:239) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:45) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseList(RoseWalker.java:52) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:67) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:40) at com.metamatrix.rose.internal.RoseImporter.parseUnits(RoseImporter.java:869) at com.metamatrix.rose.internal.RoseImporter.parseSelectedUnits(RoseImporter.java:598) at com.metamatrix.rose.internal.ui.wizard.RoseImportWizard$4.run(RoseImportWizard.java:354) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) If a model is created it is incomplete. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-585) Remove XML Service metamodel as it is no longer used.

by Ken Johnson (JIRA)

Remove XML Service metamodel as it is no longer used. ----------------------------------------------------- Key: TEIIDDES-585 URL: https://jira.jboss.org/browse/TEIIDDES-585 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: JBTools Aug 26, 2010. Eclipse 3.6, RHEL 6 Beta Reporter: Ken Johnson The XML Service metamodel is no longer used for sourcing XML data. It should be removed from Designer. -- 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, 11 months

2
1
0 / 0

[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, 11 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

13 years

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2010