February 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-505) Refactored file is not reflected in VDB (no corresponding file in workspace)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-505?page=com.atlassian.jira.plug... ] Barry LaFond edited comment on TEIIDDES-505 at 2/16/13 4:52 PM: ---------------------------------------------------------------- It's fairly straight forward to add functionality to the Refactor Command to check the workspace for VDBs containing the affected model. The biggest issues is dependencies since org.teiid.designer.ui has no access to org.teiid.designer.vdb plugin which has classes and methods to determine VDB content. Designer does have a IRefactorModelHandler extension point. Probably add a method to "pre-process" (i..e query the user) and return a boolean OK or NOT to stop/cancel or continue the refactor and possible update the VDB to reflect the refactored model. was (Author: blafond): It's fairly straight forward to add functionality to the Refactor Command to check the workspace for VDBs containing the affected model. The biggest issues is dependencies since org.teiid.designer.ui has no access to org.teiid.designer.vdb plugin which has classes and methods to determine VDB content. > Refactored file is not reflected in VDB (no corresponding file in workspace) > ---------------------------------------------------------------------------- > > Key: TEIIDDES-505 > URL: https://issues.jboss.org/browse/TEIIDDES-505 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, VDB & Execution > Affects Versions: 7.0 > Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.1 > > > I created a VDB which contained source and view models. I Refactor > Renamed one virtual model. When I opened the VDB, the original file was present and, when the mouse hovered over the file, this message was displayed, "This entry has no corresponding file in the workspace". > I believe the VDB's contents should have been involved in the refactoring, just like other files. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-505) Refactored file is not reflected in VDB (no corresponding file in workspace)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-505?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-505: --------------------------------------- It's fairly straight forward to add functionality to the Refactor Command to check the workspace for VDBs containing the affected model. The biggest issues is dependencies since org.teiid.designer.ui has no access to org.teiid.designer.vdb plugin which has classes and methods to determine VDB content. > Refactored file is not reflected in VDB (no corresponding file in workspace) > ---------------------------------------------------------------------------- > > Key: TEIIDDES-505 > URL: https://issues.jboss.org/browse/TEIIDDES-505 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, VDB & Execution > Affects Versions: 7.0 > Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.1 > > > I created a VDB which contained source and view models. I Refactor > Renamed one virtual model. When I opened the VDB, the original file was present and, when the mouse hovered over the file, this message was displayed, "This entry has no corresponding file in the workspace". > I believe the VDB's contents should have been involved in the refactoring, just like other files. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-505) Refactored file is not reflected in VDB (no corresponding file in workspace)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-505?page=com.atlassian.jira.plug... ] Barry LaFond reassigned TEIIDDES-505: ------------------------------------- Assignee: Barry LaFond (was: Dan Florian) > Refactored file is not reflected in VDB (no corresponding file in workspace) > ---------------------------------------------------------------------------- > > Key: TEIIDDES-505 > URL: https://issues.jboss.org/browse/TEIIDDES-505 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, VDB & Execution > Affects Versions: 7.0 > Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.1 > > > I created a VDB which contained source and view models. I Refactor > Renamed one virtual model. When I opened the VDB, the original file was present and, when the mouse hovered over the file, this message was displayed, "This entry has no corresponding file in the workspace". > I believe the VDB's contents should have been involved in the refactoring, just like other files. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1545) "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1545?page=com.atlassian.jira.plu... ] Dan Florian updated TEIIDDES-1545: ---------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/108 Fixed by only updating text fields if they had a different value than their data model. > "WSDL to Relational" importer fields for Source and View Model Definition Name enter backwards in Windows > --------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1545 > URL: https://issues.jboss.org/browse/TEIIDDES-1545 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.7 > Environment: Windows 7 64 bit > JBDS 5.0 > Teiid Designer Plugin version 7.7.2.v20121025-2138-H6-GA-SOA > Reporter: Debbie Steigner > Assignee: Dan Florian > Fix For: 8.1 > > > I have only found this issue on Windows JBDS installation. Import > "WSDL File or URL >> Source and View Model" proceed thru the wizard until you reach the "Models Definition" page, do not take the default names for Source. Try entering a name, the cursor returns to column 1 after each letter so hello becomes olleh. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1597) Remove the concept of extention properties for ViewImpl objects for virtual models

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1597?page=com.atlassian.jira.plu... ] Dan Florian updated TEIIDDES-1597: ---------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/107 ViewImpl is no longer available as an extended metaclass for new MEDs. If an existing MED contains a View as an extended metaclass it is a validation error. > Remove the concept of extention properties for ViewImpl objects for virtual models > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-1597 > URL: https://issues.jboss.org/browse/TEIIDDES-1597 > Project: Teiid Designer > Issue Type: Feature Request > Components: Extension Framework > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Dan Florian > Fix For: 8.1 > > > In 8.1, we're remove the ability to create New Child > View objects in virtual models. > We need to remove the ability to extend that same virtual VIEW object in the MED editor/framework. > It still needs to support older MEDs contain ViewImpl properties. This might mean a "warning"? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1472) Need look-ahead when selecting Runtime Type value for an extension property in MED Editor

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1472?page=com.atlassian.jira.plu... ] Dan Florian closed TEIIDDES-1472. --------------------------------- Release Notes Text: When keyboard focus is obtained, the runtime type combo of the MED Editor's property editor will propose matches to keystrokes. Choosing a proposal will update the runtime type. The same, look-ahead behavior is also available for extension property's display name and description for when choosing a locale. Resolution: Done Pull request merged into master branch. > Need look-ahead when selecting Runtime Type value for an extension property in MED Editor > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-1472 > URL: https://issues.jboss.org/browse/TEIIDDES-1472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Extension Framework > Affects Versions: 7.8 > Reporter: Barry LaFond > Assignee: Dan Florian > Fix For: 8.1 > > > While editing a new ModelExtensionDefinition it became annoying to have to click on "Runtime Type" combo box each time. > Would be much nicer to start typing "st" and "string" would already be selected, then type "bo" and "boolean" selected. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1472) Need look-ahead when selecting Runtime Type value for an extension property in MED Editor

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1472?page=com.atlassian.jira.plu... ] Dan Florian updated TEIIDDES-1472: ---------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/106 > Need look-ahead when selecting Runtime Type value for an extension property in MED Editor > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-1472 > URL: https://issues.jboss.org/browse/TEIIDDES-1472 > Project: Teiid Designer > Issue Type: Feature Request > Components: Extension Framework > Affects Versions: 7.8 > Reporter: Barry LaFond > Assignee: Dan Florian > Fix For: 8.1 > > > While editing a new ModelExtensionDefinition it became annoying to have to click on "Runtime Type" combo box each time. > Would be much nicer to start typing "st" and "string" would already be selected, then type "bo" and "boolean" selected. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1591: ------------------------------------------- See https://github.com/phantomjinx/teiid-designer/commit/dc027755848fb2a3ceaa... Currently under review and maybe moved to jboss tools central repository. > Improve the default eclipse dialog for entering the secure storage password > --------------------------------------------------------------------------- > > Key: TEIIDDES-1591 > URL: https://issues.jboss.org/browse/TEIIDDES-1591 > Project: Teiid Designer > Issue Type: Enhancement > Components: Eclipse Integration > Affects Versions: 8.1 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: password-provider-dialog.jpg > > > Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them! > Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1591) Improve the default eclipse dialog for entering the secure storage password

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1591?page=com.atlassian.jira.plu... ] Work on TEIIDDES-1591 started by Paul Richardson. > Improve the default eclipse dialog for entering the secure storage password > --------------------------------------------------------------------------- > > Key: TEIIDDES-1591 > URL: https://issues.jboss.org/browse/TEIIDDES-1591 > Project: Teiid Designer > Issue Type: Enhancement > Components: Eclipse Integration > Affects Versions: 8.1 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: password-provider-dialog.jpg > > > Both JBossTools and Designer use secure storage for storing passwords. As such, when opening the application and accessing secure storage for the first time (usually on starting a JBoss server), the default password dialog is displayed. However, this dialog is unintuitive since it provides little explanation of what password it is requesting and is easily confused for the JBoss / Teiid admin password or the Teiid jdbc password. Ironically, this password will allow access to both of them! > Investigation shows that the default password provider can be overridden using the org.eclipse.equinox.security.secureStorage extension point. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1571) Designer SQL expressions that differ between runtime client versions must be correct to the default server

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1571?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1571. --------------------------------------- Resolution: Done > Designer SQL expressions that differ between runtime client versions must be correct to the default server > ---------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1571 > URL: https://issues.jboss.org/browse/TEIIDDES-1571 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.1 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: 8.1 > > > Designer provides text for Text, XML and Web Service SQL transformations. Historically, this has been updated according to the included runtime client. However, with the advent of multiple runtime clients, the text must be crafted according to the active/default teiid server / runtime client. > For example, [1570|https://issues.jboss.org/browse/TEIIDDES-1570] details a fix required for the invokeHttp method's parameters in remote XML modelling. Adding a 4th parameter is correct for an 8.2 runtime client but is not correct for 7.7. > Ideally, a new service should be created, eg. IProcedureService, obtainable from the runtime clients' QueryServices. This service will allow each runtime client to return their own version of the procedure text and all such procedures in the code should delegate to this service. -- 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, 2 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 February 2013