[JBoss JIRA] Created: (TEIIDDES-885) Preview Data fails if attempted immediately after "Save" model.
by Barry LaFond (JIRA)
Preview Data fails if attempted immediately after "Save" model.
---------------------------------------------------------------
Key: TEIIDDES-885
URL: https://issues.jboss.org/browse/TEIIDDES-885
Project: Teiid Designer
Issue Type: Bug
Components: Data Preview
Affects Versions: 7.3
Reporter: Barry LaFond
Assignee: Dan Florian
Priority: Critical
Fix For: 7.4
Set up Designer with sample project with source model and connect to Teiid Instance
1) Open Package diagram for model and select Table
2) Select Preview Data action and see successful results
3) Drag diagram component and Save
4) Click Preview Data action right after click save
5) Get query result of: "Remote org.teiid.core.TeiidProcessingException: Failed to find the Connection Factory with JNDI name PREVIEW_42463872-ecd7-46dd-93b1-450354a53b55_PartsProject_PartsSourceB. Please check the name or deploy the Connection Factory with specified name."
6) Wait a few more seconds and try Preview Data again and it'll be successful
Guessing the create/deploy/redeploy VDB and maybe Data Source jobs aren't complete yet or are waiting for auto-build to run or something.
Maybe in the Preview Data action we can check the PreviewManager and stop the action of PVDB jobs are running. Or we schedule/wait the new PVDB jobs until existing are finished running.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[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
14 years, 8 months
[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
14 years, 8 months
[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
14 years, 8 months
[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