November 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2376) On windows environment, renamig a source model file's name using JBDS will broke a view model which uses the renamed source model

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2376?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2376: ---------------------------------------- When I renamed the *SourceModel_AAAAA.xmi* to *SourceModel_XXXXX* it appears that the modelImport *name* attribute isn't updated as shown below. <modelImports xmi:uuid="mmuuid:cb26ab75-2877-4cee-8efa-5de4732d18f7" name="SourceModel_AAAAA" modelLocation="SourceModel_XXXXX.xmi" On Windows the rename will incorrectly changed the <modelImports xmi:uuid="mmuuid:cb26ab75-2877-4cee-8efa-5de4732d18f7" name="SourceModel_AAAAA" modelLocation="SourceModel_AAAAA.xmi" to <modelImports xmi:uuid="mmuuid:cb26ab75-2877-4cee-8efa-5de4732d18f7" name="SourceModel_AAAAA" modelLocatiSourceModel_XXXXX.xmi.xmi" So it's OFF by *4* characters There's an <annotatedObject> href that's hosed too: <annotatedObject href="SourceModel_AAAAA.xmi#mmuuid/7291fb4c-da39-4bbc-9787-d2edd9b9551c"/> becomes SourceModel_XXXXX.xmif="SourceModel_AAAAA.xmi#mmuuid/7291fb4c-da39-4bbc-9787-d2edd9b9551c"/> I tracked the character offsets in the *RefactorResourcesUtils.calculateTextChanges()* method and for the modelImport line above, the offsets are the same on Windows AND Linux > On windows environment, renamig a source model file's name using JBDS will broke a view model which uses the renamed source model > --------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2376 > URL: https://issues.jboss.org/browse/TEIIDDES-2376 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 8.3.4 > Environment: - JBDS 7.1.1 > - JBDSIS 7.0.3 > - Windows 7 > Reporter: hisao furuichi > Assignee: Barry LaFond > Fix For: 8.6.1, 9.0.1, 9.0 > > > On windows environment, renamig a source model file's name using JBDS will broke a view model which uses the renamed source model -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2395) Add shortcut to Find Model Object in the Model Explorer Tab

by Joao Viragine (JIRA)

Joao Viragine created TEIIDDES-2395: --------------------------------------- Summary: Add shortcut to Find Model Object in the Model Explorer Tab Key: TEIIDDES-2395 URL: https://issues.jboss.org/browse/TEIIDDES-2395 Project: Teiid Designer Issue Type: Feature Request Components: Editors Affects Versions: 8.6 Reporter: Joao Viragine Priority: Minor It would be nice if we had a shortcut to "Find Model Object" in the Model Explorer Tab. It isn't productive to need to go to Menu/Search/Teiid Designer/Find Model Object every time we need to serach for a Model Object -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2388) Add SAP HANA Driver Type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2388: ---------------------------------------- Added simple connection url template if deployed SAP/HANA driver is selected in the Teiid importer's Create data source dialog. Pushing to 9.1 to allow for contributing appropriate SAP/HANA translator > Add SAP HANA Driver Type > ------------------------ > > Key: TEIIDDES-2388 > URL: https://issues.jboss.org/browse/TEIIDDES-2388 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.6.1 > Reporter: Ted Jones > Fix For: 9.1 > > > Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://{host:port}" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2388) Add SAP HANA Driver Type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2388: ----------------------------------- Fix Version/s: (was: 9.0) (was: 8.6.1) > Add SAP HANA Driver Type > ------------------------ > > Key: TEIIDDES-2388 > URL: https://issues.jboss.org/browse/TEIIDDES-2388 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.6.1 > Reporter: Ted Jones > Fix For: 9.1 > > > Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://{host:port}" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2388) Add SAP HANA Driver Type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2388: ----------------------------------- Fix Version/s: 9.1 (was: 9.0.1) > Add SAP HANA Driver Type > ------------------------ > > Key: TEIIDDES-2388 > URL: https://issues.jboss.org/browse/TEIIDDES-2388 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.6.1 > Reporter: Ted Jones > Fix For: 8.6.1, 9.0, 9.1 > > > Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://{host:port}" -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2394) Add UI support for TEXTTABLE Custom Line Separator

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2394?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2394: ----------------------------------- Fix Version/s: 9.1 > Add UI support for TEXTTABLE Custom Line Separator > --------------------------------------------------- > > Key: TEIIDDES-2394 > URL: https://issues.jboss.org/browse/TEIIDDES-2394 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Reporter: Shiveeta Mattoo > Labels: FileConnector, TEXTTABLE > Fix For: 9.1 > > > Add UI support for TEXTTABLE capability to support a Custom Line Separator . See https://docs.jboss.org/author/display/TEIID/FROM+Clause with the ROW DELIMITER char option. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1336) Properly consider further support required for the implementation of authenticated WSDLs using the 'WS-Security' security method

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1336?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1336. ------------------------------------ Resolution: Out of Date This has been addressed in Designer 8.6+ releases > Properly consider further support required for the implementation of authenticated WSDLs using the 'WS-Security' security method > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1336 > URL: https://issues.jboss.org/browse/TEIIDDES-1336 > Project: Teiid Designer > Issue Type: Sub-task > Components: Datatools Integration, Web Services Support > Affects Versions: 7.7 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: Future > > > Both teiid and designer provide the authenticated WSDL securityType choices of None, BasicHTTP and WS-Security. Consideration in the Designer connection profile and imported wizards has been focused on supporting the 'None' and 'BasicHTTP' options. The WS-Security option should also be evaluated to determine the work required to fully support it or else decide that it is currently unnecessary and thus disable/remove it. This impacts both the SOAP WSDL related importers and REST importers. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1336) Properly consider further support required for the implementation of authenticated WSDLs using the 'WS-Security' security method

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1336?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-1336. ---------------------------------- > Properly consider further support required for the implementation of authenticated WSDLs using the 'WS-Security' security method > -------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1336 > URL: https://issues.jboss.org/browse/TEIIDDES-1336 > Project: Teiid Designer > Issue Type: Sub-task > Components: Datatools Integration, Web Services Support > Affects Versions: 7.7 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: Future > > > Both teiid and designer provide the authenticated WSDL securityType choices of None, BasicHTTP and WS-Security. Consideration in the Designer connection profile and imported wizards has been focused on supporting the 'None' and 'BasicHTTP' options. The WS-Security option should also be evaluated to determine the work required to fully support it or else decide that it is currently unnecessary and thus disable/remove it. This impacts both the SOAP WSDL related importers and REST importers. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1216) New View Table Wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1216?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1216: ----------------------------------- Fix Version/s: Komodo (was: Future) > New View Table Wizard > --------------------- > > Key: TEIIDDES-1216 > URL: https://issues.jboss.org/browse/TEIIDDES-1216 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Transformations > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: Komodo > > Attachments: Create View Table Wizard.bmml, Create View Table Wizard.png, CreateViewTableWizard.png, View Easy Edit Mockup.bmml, View Easy Edit Mockup.bmml, View Easy Edit Mockup.png > > > In our push to improve usability, a new "Create View Table" wizard could provide a new means to create views using the Join or Union concept. > Result of the wizard would be a complete, valid SQL transformation that is reconciled, use "functions" in Symbol definition and include Criteria -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1149) Managing multiple versions of models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1149?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1149: ----------------------------------- Fix Version/s: Komodo Assignee: (was: Barry LaFond) Komodo release will provide a plan and and implement a framework for better collaborative model development and versioning. > Managing multiple versions of models > ------------------------------------ > > Key: TEIIDDES-1149 > URL: https://issues.jboss.org/browse/TEIIDDES-1149 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration, Modeling > Affects Versions: 7.1.1, 7.4.2 > Reporter: Tom Fonteyne > Fix For: Komodo > > > We have a big requirement to more effectively manage multiple versions of models. In the future, we will have to maintain multiple versions of models and VDBs in order to guarantee compability for some clients while possibly providing new functionality for other clients using the same models. > We will also have "core models" (again possibly multiple releases) of business concepts which will be included in VDBs for specific clients and systems, then changes will need to be merged in from this one core set to many models/VDBs in the future. I posted a question to the SME list about this a few months ago ("Effectively version controlling models"). Ramesh provided some helpful ideas, such as stacking of VDBs, which we would prefer not to do because of foreseen management and performance (query planning) problems, and also how we can deploy multiple versions of the same VDB. > The problem remains however, that the only way we have at present to work with models is interactively through Teiid designer, and the only way to merge selectively (rather than replacing models) is manually. This process would potentially have to be repeated multiple times for each changeset. The customer is concerned that this approach will become unmanageable in the future. > Being able to merge through the designer would be great, but also non-interactively and automatable in some way too. Ideally, we would like to see a greater seperation of model management from the designer (in the same that it was done in a set of reusable classes which the designer makes use of also) so we have the option of using automatable tools (ie. maven) or building or own tools to do this merging. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 5 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 November 2014