December 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-1081) Version 7.6 Release Work

by Barry LaFond (JIRA)

Version 7.6 Release Work ------------------------ Key: TEIIDDES-1081 URL: https://issues.jboss.org/browse/TEIIDDES-1081 Project: Teiid Designer Issue Type: Task Components: Build, Housekeeping Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.6 All basic work related to 7.6 release -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1189) Enabling/Disabling REST Properties Corrupts Model

by Ted Jones (Created) (JIRA)

Enabling/Disabling REST Properties Corrupts Model ------------------------------------------------- Key: TEIIDDES-1189 URL: https://issues.jboss.org/browse/TEIIDDES-1189 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.6 Reporter: Ted Jones Priority: Critical Enabling REST for procedures in a model works, but disabling REST for procedures causes the model to become corrupted. The following exceptions were found in the log after disabling and saving: !ENTRY org.teiid.designer.ui 1 0 2011-12-06 14:24:39.960 !MESSAGE The model resource for "CustomerListFile_Proc.xmi" could not be found in the workspace. If that model was being created at the time (like via an importer) this could happen and is not a problem. !STACK 0 java.lang.IllegalArgumentException: modelResource is null at com.metamatrix.core.util.CoreArgCheck.isNotNull(CoreArgCheck.java:139) at org.teiid.designer.core.extension.ModelObjectExtensionAssistant.getModelResource(ModelObjectExtensionAssistant.java:70) at org.teiid.designer.core.extension.ModelObjectExtensionAssistant.hasExtensionProperties(ModelObjectExtensionAssistant.java:229) at com.metamatrix.modeler.internal.ui.explorer.ModelExplorerLabelProvider.decorate(ModelExplorerLabelProvider.java:355) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Exception in thread "ModelBuffer.Save" java.lang.NullPointerException at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:719) at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:753) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveIDRefSingle(XMLSaveImpl.java:1972) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:298) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1318) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:90) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:592) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:256) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:206) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiResourceImpl.doSave(MtkXmiResourceImpl.java:354) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1406) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl.saveInTransaction(ModelBufferImpl.java:559) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl$1.run(ModelBufferImpl.java:488) Exception in thread "ModelBuffer.Save" java.lang.NullPointerException at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:719) at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:753) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveIDRefSingle(XMLSaveImpl.java:1972) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:298) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1318) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:90) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:592) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:256) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:206) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiResourceImpl.doSave(MtkXmiResourceImpl.java:354) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1406) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl.saveInTransaction(ModelBufferImpl.java:559) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl$1.run(ModelBufferImpl.java:488) Exception in thread "ModelBuffer.Save" java.lang.NullPointerException at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:719) at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:753) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveIDRefSingle(XMLSaveImpl.java:1972) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:298) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1318) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:90) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:592) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:256) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:206) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiResourceImpl.doSave(MtkXmiResourceImpl.java:354) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1406) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl.saveInTransaction(ModelBufferImpl.java:559) at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl$1.run(ModelBufferImpl.java:488) -- 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

13 years, 1 month

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1178) Update Users Guide to include new/changed features

by Barry LaFond (Created) (JIRA)

Update Users Guide to include new/changed features -------------------------------------------------- Key: TEIIDDES-1178 URL: https://issues.jboss.org/browse/TEIIDDES-1178 Project: Teiid Designer Issue Type: Sub-task Components: Documentation Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.6 -- 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

13 years, 1 month

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-1173) Problems With And Suggestions For The XML Source Importer

by Dan Florian (Created) (JIRA)

Problems With And Suggestions For The XML Source Importer --------------------------------------------------------- Key: TEIIDDES-1173 URL: https://issues.jboss.org/browse/TEIIDDES-1173 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.6 Environment: Teiid Designer 7.6 CR1 using Mac OS X 10.7.2 Reporter: Dan Florian Fix For: 7.6 Wizard Page 1: XML Data File Source Selection - Name text field positions caret back to the beginning after entering a character - when there is no name for the source model the model status message says "Source model does not exist." - Source model text field requires the ".xmi" extension to be entered before knowing that that model already exists. So you can continue on with the wizard if you leave off the ".xmi" even if there is a model with that name. Wizard Page 2: XML Data File Import Options Page - Selected XML Data File is editable - Could setting root path be done by a button and based on selection? Right now anything can be entered. - root path label should have a colon - splitters between the sections would be nice - Down and Up buttons remain enabled after pushing them even though there is not a selection (throws exception if pushed again) - seems like the Add button is misplaced. It should be under the xml tree since it is based on a tree selection. Maybe then "Add" could be changed to "Select As Column" or "Add as Column". - root path text field positions caret back to the beginning after entering a character - should Path be editable in Column Info? Not sure when editable how it works with root path. Wizard Page 3: View Model Definition Page - Selected data file is editable - Same problems with Name text field as other text fields. Also can't seem to delete selected characters or delete the last character. -- 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

13 years, 1 month

4
5
0 / 0

[JBoss JIRA] (TEIIDDES-1177) MED Editor - Documentation for 7.6 Release

by Barry LaFond (Created) (JIRA)

MED Editor - Documentation for 7.6 Release ------------------------------------------ Key: TEIIDDES-1177 URL: https://issues.jboss.org/browse/TEIIDDES-1177 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.6 Need documentation on the new framework. Maybe even a separate Users Guide? in addition to a section in the full users guide. -- 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

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] (TEIIDDES-1186) Teiid Designer Generating a RESTEasy War file returns no value

by Ted Jones (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1186?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1186: -------------------------------- Attachment: org.teiid.designer.dqp.ui.patch Attached project level patch compatible with Designer 7.4.2 (JBDS 4.1.1). > Teiid Designer Generating a RESTEasy War file returns no value > -------------------------------------------------------------- > > Key: TEIIDDES-1186 > URL: https://issues.jboss.org/browse/TEIIDDES-1186 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Ted Jones > Attachments: org.teiid.designer.dqp.ui.patch > > > When following the published Teiid Designer documentation on generating a RESTEasy War file, a WAR file is produced with no error and deploys successfully. When "hitting" the web service, the HTTP status of 200 is returned with an empty body when there should be a result returned. This looks to be somewhat related to: https://issues.jboss.org/browse/TEIIDDES-1124. However, when checking the generated source code, it appears to be correct. Not sure if the generated src file is the actual generated class file that is being referenced. The procedure being "wrapped" with the RESTful Web Service executes fine from a Java client. > This WAR file was generated on RHEL 6.1 (CSB) and the latest version of JBDS, 4.1.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1186) Teiid Designer Generating a RESTEasy War file returns no value

by Van Halbert (Moved) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1186?page=com.atlassian.jira.plu... ] Van Halbert moved SOA-3654 to TEIIDDES-1186: -------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-1186 (was: SOA-3654) Affects Version/s: 7.4.2 (was: 5.2.0 GA) Component/s: VDB & Execution (was: EDS) Security: (was: Public) > Teiid Designer Generating a RESTEasy War file returns no value > -------------------------------------------------------------- > > Key: TEIIDDES-1186 > URL: https://issues.jboss.org/browse/TEIIDDES-1186 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Van Halbert > > When following the published Teiid Designer documentation on generating a RESTEasy War file, a WAR file is produced with no error and deploys successfully. When "hitting" the web service, the HTTP status of 200 is returned with an empty body when there should be a result returned. This looks to be somewhat related to: https://issues.jboss.org/browse/TEIIDDES-1124. However, when checking the generated source code, it appears to be correct. Not sure if the generated src file is the actual generated class file that is being referenced. The procedure being "wrapped" with the RESTful Web Service executes fine from a Java client. > This WAR file was generated on RHEL 6.1 (CSB) and the latest version of JBDS, 4.1.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1186) Teiid Designer Generating a RESTEasy War file returns no value

by Van Halbert (Assigned) (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1186?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-1186: ------------------------------------- Assignee: Ted Jones (was: Van Halbert) > Teiid Designer Generating a RESTEasy War file returns no value > -------------------------------------------------------------- > > Key: TEIIDDES-1186 > URL: https://issues.jboss.org/browse/TEIIDDES-1186 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Debbie Steigner > Assignee: Ted Jones > > When following the published Teiid Designer documentation on generating a RESTEasy War file, a WAR file is produced with no error and deploys successfully. When "hitting" the web service, the HTTP status of 200 is returned with an empty body when there should be a result returned. This looks to be somewhat related to: https://issues.jboss.org/browse/TEIIDDES-1124. However, when checking the generated source code, it appears to be correct. Not sure if the generated src file is the actual generated class file that is being referenced. The procedure being "wrapped" with the RESTful Web Service executes fine from a Java client. > This WAR file was generated on RHEL 6.1 (CSB) and the latest version of JBDS, 4.1.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1185) Oracle DDL Parser throws exception parsing CREATE UNIQUE INDEX

by Barry LaFond (Created) (JIRA)

Oracle DDL Parser throws exception parsing CREATE UNIQUE INDEX -------------------------------------------------------------- Key: TEIIDDES-1185 URL: https://issues.jboss.org/browse/TEIIDDES-1185 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4.2 Reporter: Van Halbert Attachments: Testfile.ddl When importing a DDL file, the importer fails. Its hard to determine where the problem is in the file. It was suggested it would be nice if it could parse what it can and then indicate after which statement it failed. Also, it would be nice to be able to select which objects (like the jdbc importer of selecting tables, indexes, etc.) to import. Maybe the ddl importer could utilize part the jdbc importer wizard to provide the same options. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1176) Usability Issue: On DDL importer, need better feed back when a file cannot be imported

by Van Halbert (Created) (JIRA)

Usability Issue: On DDL importer, need better feed back when a file cannot be imported -------------------------------------------------------------------------------------- Key: TEIIDDES-1176 URL: https://issues.jboss.org/browse/TEIIDDES-1176 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4.2 Reporter: Van Halbert When importing a DDL file, the importer fails. Its hard to determine where the problem is in the file. It was suggested it would be nice if it could parse what it can and then indicate after which statement it failed. Also, it would be nice to be able to select which objects (like the jdbc importer of selecting tables, indexes, etc.) to import. Maybe the ddl importer could utilize part the jdbc importer wizard to provide the same options. -- 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

13 years, 1 month

4
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2011