[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
[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, 9 months
[JBoss JIRA] Created: (TEIIDDES-776) Data Roles: After unchecking a model, cannot check subordinate metadata, like columns
by Paul Nittel (JIRA)
Data Roles: After unchecking a model, cannot check subordinate metadata, like columns
-------------------------------------------------------------------------------------
Key: TEIIDDES-776
URL: https://issues.jboss.org/browse/TEIIDDES-776
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.1.1
Reporter: Paul Nittel
In the case where an administrator wishes to prevent access to all columns but a relatively few, they should be able to:
Uncheck the model (which causes all subordinate objects to be unchecked)
Check the small number to which access is desired.
What happens is once the model is unchecked, the subordinate objects cannot be checked. (Also, if all subordinate objects are manually unchecked, the model has a grayed-out check as if there is a checked subordinate object. If all objects under a model are unchecked, the model itself should also be unchecked.)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-812) DDL Export XSLT files need to be upgraded/improved
by Barry LaFond (JIRA)
DDL Export XSLT files need to be upgraded/improved
--------------------------------------------------
Key: TEIIDDES-812
URL: https://issues.jboss.org/browse/TEIIDDES-812
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.2, 7.1.1, 7.3
Reporter: Barry LaFond
Priority: Critical
Fix For: 7.4
After working import issue TEIIDDES-215, it's become apparent that our XSLT's for various DB's need to be revisited.
For instance, there is no logic in PostgreSQL version to check for integer types that have AUTOINCREMENT == TRUE. These should be exported as SERIAL datatypes. Same for BIGSERIAL.
There is other missing logic.
We need to:
1) Create a doc or series of docs describing what datatype conversions should be done on IMPORT JDBC and EXPORT DDL
2) Create sub-tasks for implementing these docs for all DB's
3) Possibly create extension point(s) to handle "new" DB types more effeciently
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-228) Import transformation SQL fails to do anything
by Paul Nittel (JIRA)
Import transformation SQL fails to do anything
----------------------------------------------
Key: TEIIDDES-228
URL: https://jira.jboss.org/jira/browse/TEIIDDES-228
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.2.0
Environment: Fedora 10, Designer 20090922 build (same thing with RC1)
Reporter: Paul Nittel
I exported the transformation SQL from the VQT model. When I tried to import the SQL into a new VQT model, it gave the appearance it completed successfully, but none of the tables were defined. There were no errors or exceptions found in the log.
The format of the exported file is not the same as that of the Metadata Text Importer, so to use that route the file must be edited. (The export version takes into account the SELECT, INSERT, UPDATE, DELETE possibilities.) BTW, this had issues as well, but that's another JIRA.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-181) Missing Java SQL Types In RelationalTypeMapping Interface And Implementation Class
by Dan Florian (JIRA)
Missing Java SQL Types In RelationalTypeMapping Interface And Implementation Class
----------------------------------------------------------------------------------
Key: TEIIDDES-181
URL: https://jira.jboss.org/jira/browse/TEIIDDES-181
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.0.0
Reporter: Dan Florian
The following java.sql.Types constants do not have constants in RelationalTypeMapping or mappings in RelationalTypeMappingImpl: DATALINK, BOOLEAN, ROWID, LONGNVARCHAR, NCLOB, and SQLXML. All but the first 2 were added in JDK 1.6. Need to provide the mapping to the metamatrix datatypes for each or determine a mapping is not needed.
Also may want to look at using or referencing com.metamatrix.common.types.MMJDBCSQLTypeInfo instead of maintaining the mapping in two differenct classes.
See TEIIDDES-179 where NVARCHAR was added to fix this defect.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months