January 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp

by Daniel Susín (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1570?page=com.atlassian.jira.plu... ] Daniel Susín edited comment on TEIIDDES-1570 at 1/29/13 3:42 AM: ----------------------------------------------------------------- . was (Author: dsusin): In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value. > Incorrect parameter types in invokeHttp > --------------------------------------- > > Key: TEIIDDES-1570 > URL: https://issues.jboss.org/browse/TEIIDDES-1570 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Daniel Susín > Attachments: invokeHttp_parameters.jpg > > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp

by Daniel Susín (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1570?page=com.atlassian.jira.plu... ] Daniel Susín updated TEIIDDES-1570: ----------------------------------- Description: In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value. > Incorrect parameter types in invokeHttp > --------------------------------------- > > Key: TEIIDDES-1570 > URL: https://issues.jboss.org/browse/TEIIDDES-1570 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Daniel Susín > Attachments: invokeHttp_parameters.jpg > > > In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp

by Daniel Susín (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1570?page=com.atlassian.jira.plu... ] Daniel Susín updated TEIIDDES-1570: ----------------------------------- Attachment: invokeHttp_parameters.jpg > Incorrect parameter types in invokeHttp > --------------------------------------- > > Key: TEIIDDES-1570 > URL: https://issues.jboss.org/browse/TEIIDDES-1570 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Daniel Susín > Attachments: invokeHttp_parameters.jpg > > > In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp

by Daniel Susín (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1570?page=com.atlassian.jira.plu... ] Daniel Susín commented on TEIIDDES-1570: ---------------------------------------- In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value. > Incorrect parameter types in invokeHttp > --------------------------------------- > > Key: TEIIDDES-1570 > URL: https://issues.jboss.org/browse/TEIIDDES-1570 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.0 > Reporter: Daniel Susín > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp

by Daniel Susín (JIRA)

Daniel Susín created TEIIDDES-1570: -------------------------------------- Summary: Incorrect parameter types in invokeHttp Key: TEIIDDES-1570 URL: https://issues.jboss.org/browse/TEIIDDES-1570 Project: Teiid Designer Issue Type: Bug Affects Versions: 8.0 Reporter: Daniel Susín -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1569) REST Extension Properties not Visible for Procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1569?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1569: ----------------------------------- Attachment: org.teiid.designer.dqp.patch > REST Extension Properties not Visible for Procedure > --------------------------------------------------- > > Key: TEIIDDES-1569 > URL: https://issues.jboss.org/browse/TEIIDDES-1569 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.0 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: org.teiid.designer.dqp.patch > > > REST properties (URI, PATH and METHOD) are not displaying in the properties panel for a virtual procedure. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1569) REST Extension Properties not Visible for Procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1569?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1569: ---------------------------------------- 1) The dqp plugin was not registering for model events (new model) 2) REST MED assistant did not override the applyMedIfNecessary() method to inject the namespace/MED into virtual models > REST Extension Properties not Visible for Procedure > --------------------------------------------------- > > Key: TEIIDDES-1569 > URL: https://issues.jboss.org/browse/TEIIDDES-1569 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.0 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 8.1 > > > REST properties (URI, PATH and METHOD) are not displaying in the properties panel for a virtual procedure. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1569) REST Extension Properties not Visible for Procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1569?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1569: -------------------------------------- Assignee: Barry LaFond > REST Extension Properties not Visible for Procedure > --------------------------------------------------- > > Key: TEIIDDES-1569 > URL: https://issues.jboss.org/browse/TEIIDDES-1569 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 8.0 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 8.1 > > > REST properties (URI, PATH and METHOD) are not displaying in the properties panel for a virtual procedure. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1569) REST Extension Properties not Visible for Procedure

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1569: ----------------------------------- Summary: REST Extension Properties not Visible for Procedure Key: TEIIDDES-1569 URL: https://issues.jboss.org/browse/TEIIDDES-1569 Project: Teiid Designer Issue Type: Feature Request Components: Web Services Support Affects Versions: 8.0 Reporter: Ted Jones Fix For: 8.1 REST properties (URI, PATH and METHOD) are not displaying in the properties panel for a virtual procedure. -- 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

12 years, 9 months

1
0
0 / 0

[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. 1) Import Employees.xsd in to project 2) Select "Employee" schema element in explorer and right click "Modeling > Create XML View Documents" (XML Document Model) 3) When finished it should create a XML document with mapping classes 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. !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) > 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. > 1) Import Employees.xsd in to project > 2) Select "Employee" schema element in explorer and right click "Modeling > Create XML View Documents" (XML Document Model) > 3) When finished it should create a XML document with mapping classes > 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

12 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2013