November 2011 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1164) CLONE - Index metadata should not treat cardinality 0 as unknown

by Steven Hawkins (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1164?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-1848 to TEIIDDES-1164: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-1164 (was: TEIID-1848) Affects Version/s: 6.0.0 (was: 6.0.0) Component/s: Teiid Integration (was: Query Engine) Fix Version/s: 8.0 (was: 8.0) > CLONE - Index metadata should not treat cardinality 0 as unknown > ---------------------------------------------------------------- > > Key: TEIIDDES-1164 > URL: https://issues.jboss.org/browse/TEIIDDES-1164 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Teiid Integration > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.0 > > > The default cardinality is currently 0, which is treated as unknown, however it would be better if the default were something like -1 instead. This will require introducing a new index file version (so that older vdbs with a value of 0 can be understood as meaning unknown) and updating the teiid/designer metadata defaults for cardinality as -1. -- 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-1063) Refactoring vdb with expectation to also change name only changed name of file, not name to connect to it

by Dan Florian (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1063?page=com.atlassian.jira.plu... ] Dan Florian resolved TEIIDDES-1063. ----------------------------------- Release Notes Text: Changing the VDB file name using the Refactor menu now will also change the name of the VDB in the manifest file used by the Teiid server. Resolution: Done Added processing of model-related files (those file without ModelResources) to the refactor framework. > Refactoring vdb with expectation to also change name only changed name of file, not name to connect to it > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1063 > URL: https://issues.jboss.org/browse/TEIIDDES-1063 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 7.6 > > Attachments: screenshot-1.jpg > > > Built a vdb (LookbackTest), but the name was not the one I wanted. Refactored the vdb (to Loopback) with the expectation that was the name I should see the server exposing it as. However, it only changed the name of the file, not the reference name. In designer, looking at the vdbs on the server, the old name (LoopbackTest) was still there and when I unzipped the vdb, LoopbackTest was the name in the vdb.xml. > In designer, the properties that were show when the vdb was selected, had no way to change the "name" of the vdb. It referred to the name as "Loopback.vdb", which is the filename, not the reference name. Additonally, this "name" property was not updatable. So its confusing as to how to name the vdb or change its name that I want to use when connecting via jdbc. -- 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-1163) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio

by Johnathon Lee (Created) (JIRA)

Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio ---------------------------------------------------------------------------------------------- Key: TEIIDDES-1163 URL: https://issues.jboss.org/browse/TEIIDDES-1163 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.2, 7.3, 7.4, 7.5 Environment: JBoss Developer Studio 4.0 JBoss Developer Studio 4.1 Reporter: Johnathon Lee /*+ cache */ CREATE VIRTUAL PROCEDURE SELECT 'winning'; BEGIN END The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation. com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314 The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line: this.sqlText = sqlDisplayNode.toDisplayString(); -- 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-1162) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio

by Johnathon Lee (Created) (JIRA)

Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio ---------------------------------------------------------------------------------------------- Key: TEIIDDES-1162 URL: https://issues.jboss.org/browse/TEIIDDES-1162 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.2, 7.3, 7.4, 7.5 Environment: JBoss Developer Studio 4.0 JBoss Developer Studio 4.1 Reporter: Johnathon Lee /*+ cache */ CREATE VIRTUAL PROCEDURE SELECT 'winning'; BEGIN END The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation. com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314 The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line: this.sqlText = sqlDisplayNode.toDisplayString(); -- 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-1161) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio

by Johnathon Lee (Deleted) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1161?page=com.atlassian.jira.plu... ] Johnathon Lee deleted TEIIDDES-1161: ------------------------------------ > Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1161 > URL: https://issues.jboss.org/browse/TEIIDDES-1161 > Project: Teiid Designer > Issue Type: Bug > Environment: JBoss Developer Studio 4.0 > JBoss Developer Studio 4.1 > Reporter: Johnathon Lee > > /*+ cache */ > CREATE VIRTUAL PROCEDURE > SELECT 'winning'; > BEGIN > END > The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation. > com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314 > The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line: > this.sqlText = sqlDisplayNode.toDisplayString(); -- 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-1161) Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio

by Johnathon Lee (Created) (JIRA)

Cache hint not being displayed after validation of Virtual Procedure in JBoss Developer Studio ---------------------------------------------------------------------------------------------- Key: TEIIDDES-1161 URL: https://issues.jboss.org/browse/TEIIDDES-1161 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.2, 7.3, 7.4, 7.5 Environment: JBoss Developer Studio 4.0 JBoss Developer Studio 4.1 Reporter: Johnathon Lee /*+ cache */ CREATE VIRTUAL PROCEDURE SELECT 'winning'; BEGIN END The cache hint is saved w/the Command Object even though it is not reflected in the display of the text after validation. com.metamatrix.query.internal.ui.sqleditor.component.QueryDisplayComponent:313 & 314 The Command object on these lines has a member cacheHint, holding the reference to the cacheHint, this is ignored when the sqlText is set with the line: this.sqlText = sqlDisplayNode.toDisplayString(); -- 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-1160) Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem

by Van Halbert (Assigned) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1160?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-1160: ------------------------------------- Assignee: Barry LaFond (was: Van Halbert) > Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1160 > URL: https://issues.jboss.org/browse/TEIIDDES-1160 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Priority: Critical > Fix For: 7.6 > > Attachments: CountryInfoService.wsdl > > > In Teiid Designer (JBDS) installed on Windows, the "WSDL to Relational Source Model" importer fails if the WSDL file is on the file system with "An error was encountered setting up WSDl validation.: The Content Type found at file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl, content/unknown, is not valid for WSDL. Expecting text/xml or application/xml. > com.metamatrix.modeler.modelgenerator.wsdl.validation.WSDLValidationException > 0:0 - The WSDL document file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl could not be read." > If you run the import with the URL: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL > it succeeds. If you run it on a Linux JBDS from the filesystem it succeeds. -- 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-1160) Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem

by Van Halbert (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1160?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1160: ---------------------------------- Fix Version/s: 7.6 > Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1160 > URL: https://issues.jboss.org/browse/TEIIDDES-1160 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Van Halbert > Priority: Critical > Fix For: 7.6 > > Attachments: CountryInfoService.wsdl > > > In Teiid Designer (JBDS) installed on Windows, the "WSDL to Relational Source Model" importer fails if the WSDL file is on the file system with "An error was encountered setting up WSDl validation.: The Content Type found at file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl, content/unknown, is not valid for WSDL. Expecting text/xml or application/xml. > com.metamatrix.modeler.modelgenerator.wsdl.validation.WSDLValidationException > 0:0 - The WSDL document file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl could not be read." > If you run the import with the URL: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL > it succeeds. If you run it on a Linux JBDS from the filesystem it succeeds. -- 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-1159) NPE deleting 2 linked tables in diagram

by Barry LaFond (Created) (JIRA)

NPE deleting 2 linked tables in diagram --------------------------------------- Key: TEIIDDES-1159 URL: https://issues.jboss.org/browse/TEIIDDES-1159 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 7.6 1) I created a simple 2-table relational model, created a FK between two tables 2) Save ALL 3) Select both tables in the Diagram and hit "DELETE" key get: ava.lang.IllegalArgumentException: modelResource is null at com.metamatrix.core.util.CoreArgCheck.isNotNull(CoreArgCheck.java:139) at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.getModelResource(EmfModelObjectExtensionAssistant.java:61) at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.getSupportedNamespaces(EmfModelObjectExtensionAssistant.java:237) at org.teiid.designer.extension.ModelExtensionAssistantAggregator.getSupportedNamespacePrefixes(ModelExtensionAssistantAggregator.java:104) at org.teiid.designer.extension.ModelExtensionAssistantAggregator.getPropertyDefinitions(ModelExtensionAssistantAggregator.java:62) at org.teiid.designer.ui.properties.extension.ModelExtensionPropertySource.getPropertyDescriptors(ModelExtensionPropertySource.java:65) at com.metamatrix.modeler.internal.ui.properties.ModelObjectPropertySource.getAllDescriptors(ModelObjectPropertySource.java:211) at com.metamatrix.modeler.internal.ui.properties.ModelObjectPropertySource.getPropertyDescriptors(ModelObjectPropertySource.java:309) at org.eclipse.ui.views.properties.PropertySheetEntry.computeMergedPropertyDescriptors(PropertySheetEntry.java:167) at org.eclipse.ui.views.properties.PropertySheetEntry.refreshChildEntries(PropertySheetEntry.java:530) at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:760) at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:973) at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:510) at com.metamatrix.modeler.internal.ui.properties.ModelObjectPropertySheetPage.selectionChanged(ModelObjectPropertySheetPage.java:102) at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:363) at org.eclipse.ui.internal.AbstractSelectionService.firePostSelection(AbstractSelectionService.java:179) at org.eclipse.ui.internal.AbstractSelectionService$2.selectionChanged(AbstractSelectionService.java:71) at com.metamatrix.modeler.internal.ui.editors.ModelEditorSelectionProvider$2.run(ModelEditorSelectionProvider.java:145) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at com.metamatrix.modeler.internal.ui.editors.ModelEditorSelectionProvider.fireSelectionChanged(ModelEditorSelectionProvider.java:143) at com.metamatrix.modeler.internal.ui.editors.ModelEditorSelectionProvider.setSelection(ModelEditorSelectionProvider.java:121) at com.metamatrix.modeler.internal.ui.editors.ModelEditorSelectionProvider$1.selectionChanged(ModelEditorSelectionProvider.java:43) at com.metamatrix.modeler.diagram.ui.editor.DiagramEditorSelectionProvider.fireSelectionChanged(DiagramEditorSelectionProvider.java:88) at com.metamatrix.modeler.diagram.ui.editor.DiagramEditorSelectionProvider.selectionChanged(DiagramEditorSelectionProvider.java:83) at org.eclipse.gef.ui.parts.AbstractEditPartViewer.fireSelectionChanged(AbstractEditPartViewer.java:247) at org.eclipse.gef.ui.parts.AbstractEditPartViewer$1.run(AbstractEditPartViewer.java:131) at org.eclipse.gef.SelectionManager.fireSelectionChanged(SelectionManager.java:144) at org.eclipse.gef.SelectionManager.deselect(SelectionManager.java:118) at org.eclipse.gef.ui.parts.AbstractEditPartViewer.deselect(AbstractEditPartViewer.java:202) at org.eclipse.gef.editparts.AbstractEditPart.removeNotify(AbstractEditPart.java:942) at org.eclipse.gef.editparts.AbstractGraphicalEditPart.removeNotify(AbstractGraphicalEditPart.java:823) at org.eclipse.gef.editparts.AbstractEditPart.removeChild(AbstractEditPart.java:880) at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:793) at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramEditPart.propertyChange(PackageDiagramEditPart.java:193) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) at com.metamatrix.modeler.diagram.ui.model.AbstractLocalDiagramModelNode.fireStructureChange(AbstractLocalDiagramModelNode.java:296) at com.metamatrix.modeler.diagram.ui.model.AbstractLocalDiagramModelNode.removeChild(AbstractLocalDiagramModelNode.java:151) at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramModelFactory.performRemove(PackageDiagramModelFactory.java:688) at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramModelFactory.handleSingleNotification(PackageDiagramModelFactory.java:507) at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramModelFactory.handleNotification(PackageDiagramModelFactory.java:492) at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramModelFactory.notifyModel(PackageDiagramModelFactory.java:336) at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.notifyChanged(DiagramEditor.java:1063) at com.metamatrix.modeler.internal.ui.editors.ModelEditor$5.run(ModelEditor.java:1132) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at com.metamatrix.modeler.internal.ui.actions.workers.DeleteWorker.executeCommand(DeleteWorker.java:221) at com.metamatrix.modeler.internal.ui.actions.workers.DeleteWorker.execute(DeleteWorker.java:132) at com.metamatrix.modeler.internal.ui.actions.ModelObjectAction.doRun(ModelObjectAction.java:60) at com.metamatrix.modeler.internal.ui.actions.DeleteAction.doRun(DeleteAction.java:91) -- 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

[JBoss JIRA] (TEIIDDES-1160) Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem

by Ted Jones (Commented) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1160?page=com.atlassian.jira.plu... ] Ted Jones commented on TEIIDDES-1160: ------------------------------------- Deb... have you tried importing from a path without spaces? > Teiid Designer WSDL to Relational Source Model fails if the WSDL is on a Windows filesystem > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1160 > URL: https://issues.jboss.org/browse/TEIIDDES-1160 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Van Halbert > Priority: Critical > Attachments: CountryInfoService.wsdl > > > In Teiid Designer (JBDS) installed on Windows, the "WSDL to Relational Source Model" importer fails if the WSDL file is on the file system with "An error was encountered setting up WSDl validation.: The Content Type found at file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl, content/unknown, is not valid for WSDL. Expecting text/xml or application/xml. > com.metamatrix.modeler.modelgenerator.wsdl.validation.WSDLValidationException > 0:0 - The WSDL document file://C:\Documents and Settings\debbie\Desktop\CountryInfoService.wsdl could not be read." > If you run the import with the URL: http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL > it succeeds. If you run it on a Linux JBDS from the filesystem it succeeds. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues November 2011