June 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1002) Designer requires a more flexible Model Object Refactoring framework to handle pre and post transaction events.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1002?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1002. ------------------------------------ Resolution: Out of Date Refactoring framework was re-worked to be integrated with Eclipse's framework. > Designer requires a more flexible Model Object Refactoring framework to handle pre and post transaction events. > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1002 > URL: https://issues.jboss.org/browse/TEIIDDES-1002 > Project: Teiid Designer > Issue Type: Task > Components: Modeling, Validation > Affects Versions: 7.5 > Reporter: Barry LaFond > Fix For: No Future > > > The current modeling/editing event and transaction framework in Designer cannot satisfy the requirements to perform certain cross-metamodel clean-up. > In particular, if a user Deletes a Scalar Function, the ObjectDeleteCommand results in the dependent resources (i.e. Virtual Tables and Procedures) being re-validated, which is good, but the UDFManager doesn't have a chance to de-register the affected Function model before revalidation. The resulting validation is incorrect. > Because ObjectDeleteCommand is in designer.core, there isn't any direct way that command could tell the UDFManager to perform the library clean-up. > So I propose an to expand the current "refactorModelHandler" extension point to handle this processing. > The current "RefactorModelExtensionManager" should be renamed to "RefactorModelManager" > Methods should be added such as: > preProcess(int type, Object[] objects) (Where type = DELETE, RENAME, MOVE, ADD) > postProcess(int type, Object[] objects) (Where type = DELETE, RENAME, MOVE, ADD) > Objects could be be Models, Files or EObjects -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (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 resolved TEIIDDES-382. ----------------------------------- Resolution: Won't Fix This is an Eclipse property view issue. In Komodo (future) we'll be handling designer model object properties differently > 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 > Priority: Minor > Fix For: No Future > > > 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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-704?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-704. ----------------------------------- Resolution: Out of Date > NPE while constructing XML Documents from old/custom Parts XML Schema > --------------------------------------------------------------------- > > Key: TEIIDDES-704 > URL: https://issues.jboss.org/browse/TEIIDDES-704 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.1.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: No Future > > > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-191?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-191. ----------------------------------- Resolution: Won't Fix this importer will be replaced with another framework > XSD as Relational importer has problems with child elements with many parents > ----------------------------------------------------------------------------- > > Key: TEIIDDES-191 > URL: https://issues.jboss.org/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 > Fix For: No Future > > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1746) Error setting OData CP on Source Model

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1746?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1746. --------------------------------- Resolution: Done Corrected CP logic > Error setting OData CP on Source Model > -------------------------------------- > > Key: TEIIDDES-1746 > URL: https://issues.jboss.org/browse/TEIIDDES-1746 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 8.2 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > > Error setting OData CP on source model: "No valid Teiid properties" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1746) Error setting OData CP on Source Model

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1746?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1746: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/176 > Error setting OData CP on Source Model > -------------------------------------- > > Key: TEIIDDES-1746 > URL: https://issues.jboss.org/browse/TEIIDDES-1746 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 8.2 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > > Error setting OData CP on source model: "No valid Teiid properties" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1747) Add index page to update site and simplify category.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1747?page=com.atlassian.jira.plu... ] Nick Boldt commented on TEIIDDES-1747: -------------------------------------- Build is blue, here's your update site. http://download.jboss.org/jbosstools/builds/staging/jbosstools-teiid-desi... Feel free to backport this to the 8.1.x branch if you're planning a new maintenance release there. > Add index page to update site and simplify category.xml > ------------------------------------------------------- > > Key: TEIIDDES-1747 > URL: https://issues.jboss.org/browse/TEIIDDES-1747 > Project: Teiid Designer > Issue Type: Feature Request > Components: Build > Affects Versions: 8.1, 8.2 > Reporter: Nick Boldt > Assignee: Paul Richardson > > Some minor cosmetic improvements to the Teiid Designer update site. PR forthcoming. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2013