[JBoss JIRA] (TEIIDDES-1598) Web Service and REST Procedures are Missing Return Element
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1598?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1598:
----------------------------------------
Imported attached WSDL from file system and procedures were correctly generated with Result Sets (return elements)
> Web Service and REST Procedures are Missing Return Element
> ----------------------------------------------------------
>
> Key: TEIIDDES-1598
> URL: https://issues.jboss.org/browse/TEIIDDES-1598
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Web Services Support
> Affects Versions: 8.1
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: stateService.wsdl
>
>
> When generating a web service procedure or creating a REST procedure (or any procedure that returns an element of type XML) fails to add the return element. This has to be done manually and then a restart of Eclipse is required.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1555) Errors with Web Service model operation validation
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1555?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1555:
----------------------------------------
Tested State Service WSDL import and the generated procedures looked fine and were error free.
> Errors with Web Service model operation validation
> --------------------------------------------------
>
> Key: TEIIDDES-1555
> URL: https://issues.jboss.org/browse/TEIIDDES-1555
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Transformations
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Ted Jones
> Fix For: 8.1
>
> Attachments: stateService.wsdl
>
>
> Created WS model from simple relational model.
> Validation results in the following T-editor message:
> _ERROR: TEIID30387 Could not load UDF "+", since its invocation class "org.teiid.query.function.FunctionMethods" could not be found._
> And a ClassCastException
> java.lang.ClassCastException: org.teiid82.sql.impl.xml.MappingNodeImpl cannot be cast to org.teiid.designer.xml.IMappingElement
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1116)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1196)
> 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)
> at org.teiid.designer.core.index.Index.add(Index.java:127)
> at org.teiid.designer.core.index.ModelIndexer.indexResource(ModelIndexer.java:240)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResource(ModelBuildUtil.java:308)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResources(ModelBuildUtil.java:333)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResources(ModelBuildUtil.java:324)
> at org.teiid.designer.core.builder.ModelBuildUtil.buildResources(ModelBuildUtil.java:123)
> at org.teiid.designer.core.builder.ModelBuilder$1.run(ModelBuilder.java:138)
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1555) Errors with Web Service model operation validation
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1555?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1555:
-----------------------------------
Attachment: stateService.wsdl
> Errors with Web Service model operation validation
> --------------------------------------------------
>
> Key: TEIIDDES-1555
> URL: https://issues.jboss.org/browse/TEIIDDES-1555
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Transformations
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Ted Jones
> Fix For: 8.1
>
> Attachments: stateService.wsdl
>
>
> Created WS model from simple relational model.
> Validation results in the following T-editor message:
> _ERROR: TEIID30387 Could not load UDF "+", since its invocation class "org.teiid.query.function.FunctionMethods" could not be found._
> And a ClassCastException
> java.lang.ClassCastException: org.teiid82.sql.impl.xml.MappingNodeImpl cannot be cast to org.teiid.designer.xml.IMappingElement
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1116)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1196)
> 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)
> at org.teiid.designer.core.index.Index.add(Index.java:127)
> at org.teiid.designer.core.index.ModelIndexer.indexResource(ModelIndexer.java:240)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResource(ModelBuildUtil.java:308)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResources(ModelBuildUtil.java:333)
> at org.teiid.designer.core.builder.ModelBuildUtil.indexResources(ModelBuildUtil.java:324)
> at org.teiid.designer.core.builder.ModelBuildUtil.buildResources(ModelBuildUtil.java:123)
> at org.teiid.designer.core.builder.ModelBuilder$1.run(ModelBuilder.java:138)
--
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, 9 months
[JBoss JIRA] (TEIIDDES-400) Virtual Procedure transformation editor does not properly assign data length of output parameters
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-400?page=com.atlassian.jira.plug... ]
Mark Drilling resolved TEIIDDES-400.
------------------------------------
Fix Version/s: 8.1
(was: Future)
Resolution: Done
Retests ok - the procedure column lengths are set properly. Assume fixed with another issue.
> Virtual Procedure transformation editor does not properly assign data length of output parameters
> --------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-400
> URL: https://issues.jboss.org/browse/TEIIDDES-400
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.4
> Reporter: Michael Walker
> Assignee: Mark Drilling
> Fix For: 8.1
>
>
> VPs do not properly assign data length of output parameters. It should be based on known length properties within the transformation, which can be derived from the models that are sourced, or logic defined in the transformation.
> For example, a virtual procedure does a "select firstName from mytable", and mytable has "firstName:string(255)". The output parameter for the stored procedure will be "firstName:String(10)". It should be 255 characters in length.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-1629) DDL Import Wizard has issues with 'SelectAll' / 'DeSelectAll'
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1629?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1629.
-------------------------------------
Resolution: Cannot Reproduce Bug
Retested OK, probably related to recent fix for TEIDDES-1631.
> DDL Import Wizard has issues with 'SelectAll' / 'DeSelectAll'
> -------------------------------------------------------------
>
> Key: TEIIDDES-1629
> URL: https://issues.jboss.org/browse/TEIIDDES-1629
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.0
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.1
>
>
> When re-importing (to update an existing model), the final page of the import wizard (difference report) seems to have issues with node selection.
> If a node is unchanged, you cannot select or de-select it, but when you press the 'unselectAll' button it will unselect it. After it is un-selected, you cannot reselect it.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-226) Problem importing Synonyms into VDB
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-226?page=com.atlassian.jira.plug... ]
Mark Drilling resolved TEIIDDES-226.
------------------------------------
Resolution: Done
> Problem importing Synonyms into VDB
> -----------------------------------
>
> Key: TEIIDDES-226
> URL: https://issues.jboss.org/browse/TEIIDDES-226
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration, VDB & Execution
> Affects Versions: 6.0.0, 6.1.0, 6.2.0
> Reporter: Ram Yelamanchilli
> Assignee: Mark Drilling
> Priority: Minor
> Labels: Designer, SYNONYM, VDB
> Fix For: 8.1
>
>
> I'm trying to import synonyms When I create a source model importing SYNONYM, source model is created with the following error.
> "The Base Table must reference one more more columns; there are none."
> Designer version is 6.2.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-226) Problem importing Synonyms into VDB
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-226?page=com.atlassian.jira.plug... ]
Mark Drilling updated TEIIDDES-226:
-----------------------------------
Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/118
Workaround Description:
When defining the oracle connection profile, add the following on Optional properties:
includeSynonyms=true
Workaround: Workaround Exists
Now automatically sets the connection profile optional property "includeSynonyms=true" for Oracle connection profile. Retested ok.
The user can also set this property on Connection Profile optional properties tab.
> Problem importing Synonyms into VDB
> -----------------------------------
>
> Key: TEIIDDES-226
> URL: https://issues.jboss.org/browse/TEIIDDES-226
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration, VDB & Execution
> Affects Versions: 6.0.0, 6.1.0, 6.2.0
> Reporter: Ram Yelamanchilli
> Assignee: Mark Drilling
> Priority: Minor
> Labels: Designer, SYNONYM, VDB
> Fix For: 8.1
>
>
> I'm trying to import synonyms When I create a source model importing SYNONYM, source model is created with the following error.
> "The Base Table must reference one more more columns; there are none."
> Designer version is 6.2.
--
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, 9 months
[JBoss JIRA] (TEIIDDES-226) Problem importing Synonyms into VDB
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-226?page=com.atlassian.jira.plug... ]
Mark Drilling updated TEIIDDES-226:
-----------------------------------
Fix Version/s: 8.1
(was: Future)
> Problem importing Synonyms into VDB
> -----------------------------------
>
> Key: TEIIDDES-226
> URL: https://issues.jboss.org/browse/TEIIDDES-226
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration, VDB & Execution
> Affects Versions: 6.0.0, 6.1.0, 6.2.0
> Reporter: Ram Yelamanchilli
> Assignee: Mark Drilling
> Priority: Minor
> Labels: Designer, SYNONYM, VDB
> Fix For: 8.1
>
>
> I'm trying to import synonyms When I create a source model importing SYNONYM, source model is created with the following error.
> "The Base Table must reference one more more columns; there are none."
> Designer version is 6.2.
--
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, 9 months