July 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-908) Replace Salesforce Extension Model created during import

by Barry LaFond (JIRA)

Replace Salesforce Extension Model created during import --------------------------------------------------------- Key: TEIIDDES-908 URL: https://issues.jboss.org/browse/TEIIDDES-908 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.4 In order to simplify JDBC import processing by replacing Designer's RelationalModelProcessor with Teiid's processor, the Salesforce Import use-case needs to be simplified by removing the need to have a separate Extension model. TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
14
0 / 0

[JBoss JIRA] Created: (TEIIDDES-926) Create persistance and loading mechanism for XML-based Model Extension Definitions

by Barry LaFond (JIRA)

Create persistance and loading mechanism for XML-based Model Extension Definitions ---------------------------------------------------------------------------------- Key: TEIIDDES-926 URL: https://issues.jboss.org/browse/TEIIDDES-926 Project: Teiid Designer Issue Type: Sub-task Components: Import/Export, Modeling Affects Versions: 7.4 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 7.4 Attachments: modelExtension.xsd, salesforce.mxd The New Model Extension framework requires reading (loading) and writing XML-formatted Model Extension Definition properties. These property definitions will replace the old "Extension Model" EMF construct. Attached is a sample "salesforce.mxd" (Model eXtension Definition) file and a potential backing schema -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
17
0 / 0

[JBoss JIRA] Created: (TEIIDDES-972) When importing an existing model, message notes that this is an existing model but 'Update' is not chosen by default

by Joel Tosi (JIRA)

When importing an existing model, message notes that this is an existing model but 'Update' is not chosen by default -------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-972 URL: https://issues.jboss.org/browse/TEIIDDES-972 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.2 Environment: JBDS 4.0 Reporter: Joel Tosi Priority: Minor Create a model against a relational store. Do some modeling against it Choose to import the model again Note the warning message states that the model already exists Note that the update checkbox is not checked Expected outcome is that since the message knows it is an update, the update checkbox would be checked by default -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-984) Create or update existing Test Scripts with artifacts

by Barry LaFond (JIRA)

Create or update existing Test Scripts with artifacts ----------------------------------------------------- Key: TEIIDDES-984 URL: https://issues.jboss.org/browse/TEIIDDES-984 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 7.5 Reporter: Barry LaFond Priority: Critical Fix For: 7.5 Several of the E2E and integration test scripts are outdated and need to be improved and/or cleaned up. In addition, these scripts are used by QE to create SWT Bot tests. This jira is parent task to spend some time in 7.5 release to provide up-to-date or new scripts along with compatible artifacts (XMI models, VDB's, XML Schema files, *.txt files) that can be used to create automated SWT Bot tests and to assist in better milestone and release testing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-714) Designer should clean up preview vdbs every time Teiid Server connection is made.

by Ramesh Reddy (JIRA)

Designer should clean up preview vdbs every time Teiid Server connection is made. --------------------------------------------------------------------------------- Key: TEIIDDES-714 URL: https://jira.jboss.org/browse/TEIIDDES-714 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.1 Reporter: Ramesh Reddy It is quite possible that that the preview vdbs deployed into a Teiid Server get out of sync with the Designer when the Server is restarted independent of the Designer. Since Designer keeps track of its preview vdbs based on workspace uuid, it is better that it cleans up its preview vdbs and data sources when the connection is made and connection is cleaned up. These actions may happen at both startup and shutdown of the Designer and also at the creation and discard of the Server settings once the Designer started. Otherwise there may be orphan VDBs left over in the Server. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
7
0 / 0

[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

12 years, 9 months

1
4
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

12 years, 10 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

12 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-965) Add option to generate a war with MTOM support

by Van Halbert (JIRA)

Add option to generate a war with MTOM support ---------------------------------------------- Key: TEIIDDES-965 URL: https://issues.jboss.org/browse/TEIIDDES-965 Project: Teiid Designer Issue Type: Feature Request Components: Web Services Support Affects Versions: 7.4 Reporter: Van Halbert Assignee: Ted Jones [08:51] <tejones> mus, vhalbert, it would be nice to have an option to generate a war with MTOM support as well, to avoid the user having to hack the generated war -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-981) Preview Data Action Should Let User Know When There Is Not A Default Teiid Instance Defined

by Dan Florian (JIRA)

Preview Data Action Should Let User Know When There Is Not A Default Teiid Instance Defined ------------------------------------------------------------------------------------------- Key: TEIIDDES-981 URL: https://issues.jboss.org/browse/TEIIDDES-981 Project: Teiid Designer Issue Type: Task Components: Data Preview, VDB & Execution Affects Versions: 7.4 Reporter: Dan Florian Fix For: 7.5 If there is no default Teiid instance, the Deploy VDB action displays a dialog telling the user that they need to create one in order to deploy a VDB. The Preview Data action should also do this. The Preview Data action will also need to change it's enablement policy as it should now even be enabled when there is no default Teiid instance. It would also be nice if both actions provided access to the "New Teiid Instance" wizard. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2011