[JBoss JIRA] (TEIIDDES-1568) NPEs resulting from null parent mapping nodes on XML Document creation from schema
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1568?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1568:
-----------------------------------
Attachment: Employees.xsd
> NPEs resulting from null parent mapping nodes on XML Document creation from schema
> ----------------------------------------------------------------------------------
>
> Key: TEIIDDES-1568
> URL: https://issues.jboss.org/browse/TEIIDDES-1568
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
> Attachments: Employees.xsd
>
>
> While trying to create simple XML document for "Employee" from the attached Employees.xsd schema, there were NPE's.
> Tracked in Debug and seems the created MappingDocument class does not have it's variable "parent" set which is required to walk the mapping nodes and create children.
> !ENTRY org.teiid.designer.transformation 4 0 2013-01-28 08:29:47.504
> !MESSAGE
> !STACK 0
> java.lang.NullPointerException
> at org.teiid82.sql.impl.xml.MappingDocumentFactory.addNamespace(MappingDocumentFactory.java:66)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createNamespaceAttribute(MappingDocumentFormatter.java:833)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1118)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1198)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createDocumentNode(MappingDocumentFormatter.java:702)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:748)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMappingString(MappingDocumentFormatter.java:821)
> at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformation(TreeMappingRootSqlAspect.java:285)
> at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformationInfo(TreeMappingRootSqlAspect.java:333)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172)
> at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311)
> at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164)
--
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
11 years, 11 months
[JBoss JIRA] (TEIIDDES-1568) NPEs resulting from null parent mapping nodes on XML Document creation from schema
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1568?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1568:
-----------------------------------
Description:
While trying to create simple XML document for "Employee" from the attached Employees.xsd schema, there were NPE's.
Tracked in Debug and seems the created MappingDocument class does not have it's variable "parent" set which is required to walk the mapping nodes and create children.
!ENTRY org.teiid.designer.transformation 4 0 2013-01-28 08:29:47.504
!MESSAGE
!STACK 0
java.lang.NullPointerException
at org.teiid82.sql.impl.xml.MappingDocumentFactory.addNamespace(MappingDocumentFactory.java:66)
at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createNamespaceAttribute(MappingDocumentFormatter.java:833)
at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787)
at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1118)
at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1198)
at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createDocumentNode(MappingDocumentFormatter.java:702)
at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:748)
at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMappingString(MappingDocumentFormatter.java:821)
at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformation(TreeMappingRootSqlAspect.java:285)
at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformationInfo(TreeMappingRootSqlAspect.java:333)
at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412)
at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172)
at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311)
at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164)
was:
While trying to create simple XML document for "Employee" from the attached Employees.xsd schema, there were NPE's.
Tracked in Debug and seems the created MappingDocument class does not have it's variable "parent" set which is required to walk the mapping nodes and create children.
> NPEs resulting from null parent mapping nodes on XML Document creation from schema
> ----------------------------------------------------------------------------------
>
> Key: TEIIDDES-1568
> URL: https://issues.jboss.org/browse/TEIIDDES-1568
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> While trying to create simple XML document for "Employee" from the attached Employees.xsd schema, there were NPE's.
> Tracked in Debug and seems the created MappingDocument class does not have it's variable "parent" set which is required to walk the mapping nodes and create children.
> !ENTRY org.teiid.designer.transformation 4 0 2013-01-28 08:29:47.504
> !MESSAGE
> !STACK 0
> java.lang.NullPointerException
> at org.teiid82.sql.impl.xml.MappingDocumentFactory.addNamespace(MappingDocumentFactory.java:66)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createNamespaceAttribute(MappingDocumentFormatter.java:833)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1118)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1198)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createDocumentNode(MappingDocumentFormatter.java:702)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:748)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMappingString(MappingDocumentFormatter.java:821)
> at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformation(TreeMappingRootSqlAspect.java:285)
> at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformationInfo(TreeMappingRootSqlAspect.java:333)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172)
> at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311)
> at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164)
--
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
11 years, 11 months
[JBoss JIRA] (TEIIDDES-1568) NPEs resulting from null parent mapping nodes on XML Document creation from schema
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1568:
--------------------------------------
Summary: NPEs resulting from null parent mapping nodes on XML Document creation from schema
Key: TEIIDDES-1568
URL: https://issues.jboss.org/browse/TEIIDDES-1568
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 8.1
Reporter: Barry LaFond
Assignee: Paul Richardson
Fix For: 8.1
While trying to create simple XML document for "Employee" from the attached Employees.xsd schema, there were NPE's.
Tracked in Debug and seems the created MappingDocument class does not have it's variable "parent" set which is required to walk the mapping nodes and create children.
--
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
11 years, 11 months
[JBoss JIRA] (TEIIDDES-1111) Create a model(s) (view/source) based on the schema and type of data source provided
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1111?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1111:
-----------------------------------
Fix Version/s: Future
(was: 8.1)
We need to integrate this with the Scalar to XML and XML to Scalar actions (on XSD). Gonna take a re-design. Pushing to future... 8.2??
> Create a model(s) (view/source) based on the schema and type of data source provided
> ------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1111
> URL: https://issues.jboss.org/browse/TEIIDDES-1111
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Labels: importers, teiid, xml
> Fix For: Future
>
>
> There have been many requests from users in the recent past to auto-generate source and view models that can consume the XML coming in the specified in a schema file. The current XML document model, take in a XSD and maps the relational data into XML data. This request is exact opposite of it in the consuming side. The data is coming in as XML, need to expose them as relational.
> I strongly believe that this needs to be done as part of TEIIDDES-1078, not create separate importers to minimize the user experience with modelling any XML data.
> The data sources can File, SOAP service or Rest service currently, but may not be restricted to those.
--
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
11 years, 11 months
[JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1010:
----------------------------------------
Van, could you find/set up on one of our testing boxes a Schema that will return multiple tables/indexes where the PK is unnamed so I can use it to test/fix this?
thx
> Indexes are not qualified when imported with Teiid Designer
> -----------------------------------------------------------
>
> Key: TEIIDDES-1010
> URL: https://issues.jboss.org/browse/TEIIDDES-1010
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.4
> Reporter: Marc Shirley
> Assignee: Barry LaFond
> Fix For: 8.1
>
>
> Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages.
--
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
11 years, 11 months
[JBoss JIRA] (TEIIDDES-1550) Errors in transformations and opening transformation editor
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1550?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1550.
---------------------------------------
Resolution: Done
> Errors in transformations and opening transformation editor
> -----------------------------------------------------------
>
> Key: TEIIDDES-1550
> URL: https://issues.jboss.org/browse/TEIIDDES-1550
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Transformations
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Priority: Blocker
> Fix For: 8.1
>
> Attachments: TEIIDDES-1550.zip
>
>
> Attaching project set with 2 projects
> 1) Simple Parts view transformation results in validation error;
> * Select * FROM PartsSupplier.SHIP_VIA
> * ERROR: The name of a symbol may not be null.
> 2) Imported Flat File to create text file procedure
> * Opening Transformation Editor results in error
> * ERROR: Caused by: java.lang.IllegalArgumentException: RuntimeTypeConverter.getRuntimeType:Object type cannot be determined for <A.SYMBOL>.
--
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
11 years, 11 months
[JBoss JIRA] (TEIIDDES-1565) Convert teiid runtime libraries to source compiled plugins
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1565?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1565.
---------------------------------------
Resolution: Done
> Convert teiid runtime libraries to source compiled plugins
> ----------------------------------------------------------
>
> Key: TEIIDDES-1565
> URL: https://issues.jboss.org/browse/TEIIDDES-1565
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Teiid Integration
> Affects Versions: 8.1
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> To remove the use of delegate wrapping classes, which are a major source of bugs, convert the teiid 7.7.2 and 8.2.x plugins to teiid source compiling plugins rather than current jar wrapping plugins.
> To achieve this:
> 1. Create plugins are git submodules so that the latest branch source code is cloned. (use fork of teiid repository since other commits will be added on top)
> 2. Modify the teiid project to eclipsify
> 3. Modify the poms to use tycho for building plugins rather than autonomous jar archives
> 4. Ensure tests all work both in eclipse and jenkins
> 5. Remove the delegate wrapping classes and append the spi interfaces to the teiid classes.
--
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
11 years, 11 months
[JBoss JIRA] (TEIIDDES-1150) Model Extension Definition Problem Markers For Models Should Support Quick Fix
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1150?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-1150:
------------------------------------
Fix Version/s: Future
(was: 8.1)
pushing to next release
> Model Extension Definition Problem Markers For Models Should Support Quick Fix
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-1150
> URL: https://issues.jboss.org/browse/TEIIDDES-1150
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Editors
> Affects Versions: 7.6
> Reporter: Dan Florian
> Assignee: Mark Drilling
> Fix For: Future
>
>
> Model problem markers related to MEDs should have a quick fix option. Currently there are 2 MED problem markers:
> (1) MED found in model is not registry. Quick fix should offer to save that MED to a file in the workspace.
> (2) MED found in model is different than the same MED in the registry. Quick fix should offer to update the model to the registry copy of the MED.
> I'm thinking that the quick fix in each case would not offer to fix all markers of the same error at the same time. However, the quick fix for (1) could offer to save all MEDs in a common directory. And the quick fix for (2) could offer to update all models to the MED version. These options might be nice and deserve more thought.
--
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
11 years, 11 months
[JBoss JIRA] (TEIIDDES-1417) Problems After Renaming Model Which Is A Dependency For Other Models
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1417?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-1417:
------------------------------------
Fix Version/s: Future
(was: 8.1)
pushing to next release.
> Problems After Renaming Model Which Is A Dependency For Other Models
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1417
> URL: https://issues.jboss.org/browse/TEIIDDES-1417
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7.1
> Reporter: Dan Florian
> Assignee: Mark Drilling
> Fix For: Future
>
>
> After renaming a virtual model that is a dependency of many other models, the following error sometimes occurs:
> Unresolved reference "file:/<file_path_to_base_model>/<name_of_old_base_model>"
> Seems may have something to do with model object proxies and loading of models. If all the models are open in an editor, the error will not occur. However, if no editors are open, the error may occur.
> The error is generated from the ResourceInScopeValidationRule class when an EMF resource cannot be found.
> See forum post for more details.
--
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
11 years, 11 months