January 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-104) F2 Rename dialog needs selected object context (i.e. Model name, Object location & Metaclass type)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-104?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-104. ----------------------------------- Resolution: Done Done > F2 Rename dialog needs selected object context (i.e. Model name, Object location & Metaclass type) > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-104 > URL: https://issues.jboss.org/browse/TEIIDDES-104 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 6.0.0 > Environment: 5.5.3 Designer > Reporter: Jerry Helbling > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.1 > > Attachments: rename-model-object-dialog.png > > > In Web Service Operation Editor, using F2 to rename the selected Input Variable renames the Operation instead. Right click - Rename works fine, but many users are used to using F2 to rename. If we do not choose to support F2 when we have selected a variable in Input Variables, or an Operation in the Operations tree, then we should make sure it does nothing. If we do want to support F2 for renaming, then it should rename the selected object, not the Operation. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-104) F2 Rename dialog needs selected object context (i.e. Model name, Object location & Metaclass type)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-104?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-104: ---------------------------------- Attachment: rename-model-object-dialog.png Added object location and type to dialog Added string name validation to prevent name errors > F2 Rename dialog needs selected object context (i.e. Model name, Object location & Metaclass type) > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-104 > URL: https://issues.jboss.org/browse/TEIIDDES-104 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 6.0.0 > Environment: 5.5.3 Designer > Reporter: Jerry Helbling > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.1 > > Attachments: rename-model-object-dialog.png > > > In Web Service Operation Editor, using F2 to rename the selected Input Variable renames the Operation instead. Right click - Rename works fine, but many users are used to using F2 to rename. If we do not choose to support F2 when we have selected a variable in Input Variables, or an Operation in the Operations tree, then we should make sure it does nothing. If we do want to support F2 for renaming, then it should rename the selected object, not the Operation. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1555) Errors with Web Service model operation validation

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1555: -------------------------------------- Summary: 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: Paul Richardson Fix For: 8.1 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1554) Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1554?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-1554: ---------------------------------- Attachment: portfolio.zip Project set > Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x > ---------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1554 > URL: https://issues.jboss.org/browse/TEIIDDES-1554 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations, Validation > Affects Versions: 8.0 > Environment: jbdevstudio-product-universal-6.0.0.GA-v20121206-1855-B186.jar > Designer 8 final release > Reporter: Van Halbert > Attachments: portfolio.zip > > > Taking a project set built in the latest JDBS 5 / Designer 7.x and trying to validate it in Designer 8. > The MartketDataView.StockPrices view has this error: > Found problems validating transformation defining MarketDataView/StockPrices, re-validate in the transformation editor. > Unable to to get the error to go away after revalidating. Also tried the quick fix with no luck. Also tried typing in spaces to trigger revalidation, no luck. > No error messages in the .log. Attached the project set. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1554) Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1554: ------------------------------------- Summary: Unable to validate transformation in project set in Designer 8 where the project was built in Designer 7.x Key: TEIIDDES-1554 URL: https://issues.jboss.org/browse/TEIIDDES-1554 Project: Teiid Designer Issue Type: Bug Components: Transformations, Validation Affects Versions: 8.0 Environment: jbdevstudio-product-universal-6.0.0.GA-v20121206-1855-B186.jar Designer 8 final release Reporter: Van Halbert Attachments: portfolio.zip Taking a project set built in the latest JDBS 5 / Designer 7.x and trying to validate it in Designer 8. The MartketDataView.StockPrices view has this error: Found problems validating transformation defining MarketDataView/StockPrices, re-validate in the transformation editor. Unable to to get the error to go away after revalidating. Also tried the quick fix with no luck. Also tried typing in spaces to trigger revalidation, no luck. No error messages in the .log. Attached the project set. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1386) Cannot multi-select schema contents when building response procedure result set (Web Service as input)

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1386?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1386: -------------------------------- Fix Version/s: Komodo (was: 8.1) > Cannot multi-select schema contents when building response procedure result set (Web Service as input) > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1386 > URL: https://issues.jboss.org/browse/TEIIDDES-1386 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.7.1 > Reporter: Paul Nittel > Assignee: Ted Jones > Fix For: Komodo > > Attachments: CannotMultiSelect.png > > > When modeling the response result set for an incoming Web Service, the user must select each attribute individually and click the Add button. Intuitively, I tried to multi-select the attributes, but that is not permitted. It should be. :-) Screenshot is attached. > I used the Oorsprong FullCountryInfo operation which has several output attributes from which to choose. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1304) Add CRUD Support to OData Importer

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1304?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1304: -------------------------------- Fix Version/s: Komodo (was: 8.1) > Add CRUD Support to OData Importer > ---------------------------------- > > Key: TEIIDDES-1304 > URL: https://issues.jboss.org/browse/TEIIDDES-1304 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: Komodo > > > Need to add CRUD support to the OData Importer (https://issues.jboss.org/browse/TEIIDDES-1303). -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1303) Create OData Importer

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1303?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1303: -------------------------------- Fix Version/s: Komodo (was: 8.1) > Create OData Importer > --------------------- > > Key: TEIIDDES-1303 > URL: https://issues.jboss.org/browse/TEIIDDES-1303 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 7.7 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: Komodo > > > To provide support for more complicated OData use cases, we should extend the XML Importer to create an OData importer. This importer will read the metadata of the service in the selected CP and determine what columns are allowable for input. We would then need to create an access pattern on the generated base table for these fields. These fields would be added to the URL of the service.. so the above Bank service URL would become: > http://gw.esworkplace.sap.com/sap/opu/sdata/sap/DEMO_BANK/z_demo_bankColl... > and the generated transformation should take the column values from the access pattern and build the URL accordingly in the invokeHttp() call. -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1436) Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1436?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1436: -------------------------------- Fix Version/s: Future (was: 8.1) > Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-1436 > URL: https://issues.jboss.org/browse/TEIIDDES-1436 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 7.7.1 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: Future > > Attachments: foo.zip > > > "Document models can be created that have nested namespaces, and Teiid contains code to use different namespace prefixes for nested elements. However at least for my simple test case (see attached) the generated mapping document does not contain any namespaceURI information for the elements - it only has the namespace declarations. It would appear that the logic in MappingDocumentFormatter is not correctly associating the prefix/uri with elements at least for a simple hand made document model. I don't know if things are different when starting with a schema." - SteveH -- 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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1305) Add Support for SAP Annotations

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1305?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1305: -------------------------------- Fix Version/s: Future (was: 8.1) > Add Support for SAP Annotations > ------------------------------- > > Key: TEIIDDES-1305 > URL: https://issues.jboss.org/browse/TEIIDDES-1305 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.7 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: Future > > > Need to support SAP annotations for accessing SAP Gateway services. This may require adding the SAP OData SDK to the Designer. -- 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

13 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2013