August 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-704) NPE while constructing XML Documents from old/custom Parts XML Schema

by Barry LaFond (JIRA)

NPE while constructing XML Documents from old/custom Parts XML Schema --------------------------------------------------------------------- Key: TEIIDDES-704 URL: https://jira.jboss.org/browse/TEIIDDES-704 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Reporter: Barry LaFond Fix For: 7.2 TEIIDDES-664 exposed a problem with displaying a error dialog when XML Document creation fails. This was fixed. What's not fixed is the NPE that is resulting from the schema involved. See attached Schema and create an XML Document from the PartOrder root element. 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.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.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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
4
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-315) Designer properties tab jumps to a seemingly random location in the properties list when any object is selected

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-315?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-315: ---------------------------------- Fix Version/s: 8.0 (was: 7.5) Affects Version/s: 7.5 > Designer properties tab jumps to a seemingly random location in the properties list when any object is selected > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-315 > URL: https://issues.jboss.org/browse/TEIIDDES-315 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 7.5 > Reporter: Michael Walker > Assignee: Dan Florian > Fix For: 8.0 > > > Open a view model, click on a column of a view. The properties tab will skip down to the near-bottom of the list of properties. Perhaps it should display the top of the list, assuming you are clicking on a column for the first time. Scrolling to the near-bottom is a bug. > Now move the scroll bar for the properties window up to the top, and edit some property. Click on another column, as if you were going to edit the same property. > The properties tab will once again skip to the near-bottom of the list of properties. > Instead, it should remain wherever it previously was. This will facilitate quicker editing of the same property on multiple objects of the same type. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-382) Clicking on almost any model property results in incorrect description being displayed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-382?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-382: ---------------------------------- Fix Version/s: 8.0 (was: 7.5) > Clicking on almost any model property results in incorrect description being displayed > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-382 > URL: https://issues.jboss.org/browse/TEIIDDES-382 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 7.4 > Reporter: Michael Walker > Assignee: Dan Florian > Priority: Minor > Fix For: 8.0 > > > Click on a property of a column. Below, you will see: > i. NameInSource of Entity > This is likely to be the description of the "NameInSource" property. We incorrectly assign the same description to every other property. This is not helpful. > Each property should have an accurate description that informs the user what the property represents. They should not have to do to the PDF documentation every time to look this information up - it's too tedious. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-1026) Teiid Designer "Import from JDBC" for SQL Server only shows dbo schema under the "Select Data Objects" screen

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1026?page=com.atlassian.jira.plu... ] Van Halbert moved SOA-3257 to TEIIDDES-1026: -------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise SOA Platform) Key: TEIIDDES-1026 (was: SOA-3257) Affects Version/s: 7.4 (was: 5.1.0 GA) Component/s: Import/Export (was: EDS) Security: (was: Public) > Teiid Designer "Import from JDBC" for SQL Server only shows dbo schema under the "Select Data Objects" screen > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1026 > URL: https://issues.jboss.org/browse/TEIIDDES-1026 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > > Teiid Designer "Import from JDBC" for SQL Server only shows dbo schema under the "Select Data Objects" screen. If a SQL Server database has multiple schemas underneath it, the importer will not show them, so you will be unable to choose and import the tables under any other schema besides dbo. I've attached a printscreen document explaining further. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-979) Add to the documentation what metadata used in designer has a material impact on runtime

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-979?page=com.atlassian.jira.plug... ] Van Halbert updated TEIIDDES-979: --------------------------------- Fix Version/s: 7.4.2 In the community, a discussion (http://community.jboss.org/thread/170698) has been started to gather this information for documentation. > Add to the documentation what metadata used in designer has a material impact on runtime > ---------------------------------------------------------------------------------------- > > Key: TEIIDDES-979 > URL: https://issues.jboss.org/browse/TEIIDDES-979 > Project: Teiid Designer > Issue Type: Enhancement > Components: Documentation > Affects Versions: 7.1.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 7.4.2 > > > Add to the documentation what metadata used in designer has a material impact on runtime -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1019) java.lang.NullPointerException importing OnHand.wsdl via Import > Teiid Designer > WSDL into Web Service Model

by Barry LaFond (JIRA)

java.lang.NullPointerException importing OnHand.wsdl via Import > Teiid Designer > WSDL into Web Service Model -------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-1019 URL: https://issues.jboss.org/browse/TEIIDDES-1019 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.5 Reporter: Barry LaFond Assignee: Ted Jones Priority: Blocker Fix For: 7.5 Import attached OnHand.wsdl file via Import > Teiid Designer > WSDL into Web Service Model Results in: java.lang.NullPointerException at com.metamatrix.modeler.webservice.procedure.XsdInstanceNode.<init>(XsdInstanceNode.java:132) at com.metamatrix.modeler.webservice.procedure.XsdInstanceNode.<init>(XsdInstanceNode.java:72) at com.metamatrix.modeler.webservice.util.WebServiceUtil.addInputVariables(WebServiceUtil.java:405) at com.metamatrix.modeler.webservice.util.WebServiceUtil.generateTransformationSql(WebServiceUtil.java:299) at com.metamatrix.modeler.internal.webservice.gen.BasicWebServiceXmlDocumentGenerator.doGenerateTransformation(BasicWebServiceXmlDocumentGenerator.java:371) at com.metamatrix.modeler.internal.webservice.gen.BasicWebServiceXmlDocumentGenerator.doGenerate(BasicWebServiceXmlDocumentGenerator.java:235) at com.metamatrix.modeler.internal.webservice.gen.BasicWebServiceXmlDocumentGenerator.generate(BasicWebServiceXmlDocumentGenerator.java:195) at com.metamatrix.modeler.internal.webservice.XmlDocumentModelProducer.execute(XmlDocumentModelProducer.java:95) at com.metamatrix.modeler.compare.generator.BasicModelGenerator$1.run(BasicModelGenerator.java:116) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:542) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:585) at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:485) at com.metamatrix.modeler.compare.generator.BasicModelGenerator.doGenerateOutput(BasicModelGenerator.java:128) at com.metamatrix.modeler.compare.generator.AbstractModelGenerator.generateOutput(AbstractModelGenerator.java:164) at com.metamatrix.modeler.compare.generator.CompositeModelGenerator.doGenerateOutput(CompositeModelGenerator.java:99) at com.metamatrix.modeler.compare.generator.AbstractModelGenerator.execute(AbstractModelGenerator.java:103) at com.metamatrix.modeler.internal.webservice.ui.wizard.WsdlFileSystemImportWizard.runFinish(WsdlFileSystemImportWizard.java:358) at com.metamatrix.modeler.internal.webservice.ui.wizard.WsdlFileSystemImportWizard$2.run(WsdlFileSystemImportWizard.java:262) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
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: ----------------------------------- Fix Version/s: 8.0 > 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 > Fix For: 8.0 > > > 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

14 years, 8 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1009: --------------------------------------- Is this being included in TEIIDDES-1017 changes? > 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

14 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-990) Add JSON Support to Generated REST War

by Ted Jones (JIRA)

Add JSON Support to Generated REST War -------------------------------------- Key: TEIIDDES-990 URL: https://issues.jboss.org/browse/TEIIDDES-990 Project: Teiid Designer Issue Type: Enhancement Components: Web Services Support Affects Versions: 7.4 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.5 Currently, the generated RESTEasy war accepts URI parameters and XML and produces only XML. We need to ad support for JSON as input and output as well as provide a way to determine which one to use. We could perhaps generate methods for both and return XML for XML inputs and JSON for JSON inputs. Another option would be to default to XML (or JSON) and allow an override via an extended property on the procedure. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1013) REST WAR Generation Action is Case-Sensitive in Regards to RESTful Extended Properties

by Ted Jones (JIRA)

REST WAR Generation Action is Case-Sensitive in Regards to RESTful Extended Properties -------------------------------------------------------------------------------------- Key: TEIIDDES-1013 URL: https://issues.jboss.org/browse/TEIIDDES-1013 Project: Teiid Designer Issue Type: Bug Components: Web Services Support Affects Versions: 7.4 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.5, 7.4 The two extended properties required for RESTful procedures are "REST-METHOD" and "URI". The check in the action for these properties expects the properties names to be upper-case. We should allow for lower case as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2011