April 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-407) Replace Designer's workspace source binding management framework with Server-managed framework

by Barry LaFond (JIRA)

Replace Designer's workspace source binding management framework with Server-managed framework ---------------------------------------------------------------------------------------------- Key: TEIIDDES-407 URL: https://jira.jboss.org/jira/browse/TEIIDDES-407 Project: Teiid Designer Issue Type: Sub-task Components: Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Source bindings were managed in 6.3 Designer. The Teiid API provides assignBindingToModel() method for VDB's deployed to Teiid. By creating a "hidden" VDB for each running Server, we can manager these source bindings via that hidden VDB. This will required Creating the hidden VDB, managing it's life cycle, providing utility methods to assign/remove source bindings based on model edits (Delete/Rename) etc.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-412) Expose Bound Workspace models in Execution View for each Teiid Server

by Barry LaFond (JIRA)

Expose Bound Workspace models in Execution View for each Teiid Server --------------------------------------------------------------------- Key: TEIIDDES-412 URL: https://jira.jboss.org/jira/browse/TEIIDDES-412 Project: Teiid Designer Issue Type: Sub-task Components: VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 To assist the user in both creating/changing and viewing workspace source-to-connector bindings, show a "workspace models" root under each Teiid Server root showing each bound model and it's current connector binding. The reverse of this is to maintain a "connector-to-source" binding object in the Model Explorer view for each source model. (if bound) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-408) Adapt Designer's Connector framework to Teiid JCA connector changes

by Barry LaFond (JIRA)

Adapt Designer's Connector framework to Teiid JCA connector changes ------------------------------------------------------------------- Key: TEIIDDES-408 URL: https://jira.jboss.org/jira/browse/TEIIDDES-408 Project: Teiid Designer Issue Type: Sub-task Components: Import/Export, Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 Designer's access to old Teiid "ConnectorBinding","ComponentType" and "ComponentTypeID" are now gone and replaced with: ConnectorBinding ConnectorType Need to re-place with new classes and utilize direct access to Teiid via API. - Replace ConfigurationManager with Server Manager and Execution Manager classes - Wrap Connector Bindings and Connector Types to faciliate re-use of some of existing framework. - (minimum impact) - Create and manage "Server" objects - Remove all "Jar" management functionality from Designer (UDF's and JDBC Drivers (see 9)) - Connector Validation - Reimplement binding creation for the WSDL to Relational importer around new admin API. (TEIIDDES-265) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-263) Perform general housekeeping duties on 7.0 Codebase. Remove unnecessary code (class, methods and fields) refactor, repackage, etc.

by Barry LaFond (JIRA)

Perform general housekeeping duties on 7.0 Codebase. Remove unnecessary code (class, methods and fields) refactor, repackage, etc. ---------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-263 URL: https://jira.jboss.org/jira/browse/TEIIDDES-263 Project: Teiid Designer Issue Type: Task Components: Housekeeping Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Teiid Designer code-base is basically 10 years old. Included are recent inherited code from Teiid. We need to perform basic house-cleaning duties to make sure we don't carry forward any more code than we need to. So: 1) Remove unnecessary code 2) Repackage code into plugins and packages that make sense 3) Clarify "internal" code in our packaging scheme -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-405) Provide one or more views for Teiid Server Management

by Barry LaFond (JIRA)

Provide one or more views for Teiid Server Management ----------------------------------------------------- Key: TEIIDDES-405 URL: https://jira.jboss.org/jira/browse/TEIIDDES-405 Project: Teiid Designer Issue Type: Task Components: Teiid Integration, VDB & Execution, Views Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 Provide one or more views for Server Management With new paradigm of "servers" within Designer and working with JBTools the requirement of a Designer "Servers" view was created. It is envisioned that this view should combine as a minimum the Teiid Server, Connector Types, Connectors, Source Bindings and Deployed VDB's - ? One view for all types (JBoss/EAP/Teiid/ModeShape, etc....) - ? or one for each type - WTP Server View?? - add Refresh button/action - Teiid Server View. So the basic view will contain a tree of Teiid Servers who's children include: - SERVER 1)CONNECTOR TYPE - CONNECTORS - SOURCES 2)VDB's (Stretch goal) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-404) Facilitate deployment of VDB's from Designer to Teiid Server

by Barry LaFond (JIRA)

Facilitate deployment of VDB's from Designer to Teiid Server ------------------------------------------------------------ Key: TEIIDDES-404 URL: https://jira.jboss.org/jira/browse/TEIIDDES-404 Project: Teiid Designer Issue Type: Task Components: Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 As part of 7.0 Teiid integration, both Preview Data and VDB Execution are going to required deployment of workspace VDB's to Teiid. This can be done by Right-click VDB "Deploy to Teiid" action or DND to Teiid Server in Server/Execution View -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-424) New Connector UI (Dialog, Panel) Has Several Problems

by Dan Florian (JIRA)

New Connector UI (Dialog, Panel) Has Several Problems ----------------------------------------------------- Key: TEIIDDES-424 URL: https://jira.jboss.org/jira/browse/TEIIDDES-424 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 7.0 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.0 Here are 3 problems: (1) the new connector dialog and panel i8n is not working, (2) the correct connector type is not being selected when the dialog opens, and (3) the dialog message indicates the connector name is empty when it is not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-176) Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs.

by Ramesh Reddy (JIRA)

Desinger needs to embed "Teiid Embedded" as a plugin, with only dependencies to "public" APIs. ---------------------------------------------------------------------------------------------- Key: TEIIDDES-176 URL: https://jira.jboss.org/jira/browse/TEIIDDES-176 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: Ramesh Reddy Assignee: Johnny Verhaeg Priority: Critical > On Wed, 2009-05-06 at 11:35 -0400, John Doyle wrote: >> I'm throwing this idea out there with very little idea of how the >> links between Teiid and Designer function, but I think it would be >> cool and beneficial. >> >> AFAIK we don't have a user story abut how you update the version of >> Teiid that is delivered with Designer. I think that it would be >> very cool if we exposed this cabability in designer similar to the >> way Installed JREs are exposed through the Preferences page. >> Designer could come with a version of Teiid, but users could point >> Designer to other versions of Teiid installed on their system and >> choose to run with those. One of the goals we have discussed is >> that we don't want Designer to be wedded to a particular version of >> Teiid. Defining the links between to two in this manner would >> force a contract and make it easy to test and validate that >> Designer 6.X works with Teiid 6.X and 7.X, etc. >> >> What do you think? > Well that is certainly the case going forward to have such modularity, > as this has been discussed before. However, that is not case today. > There needs to be huge re-work needs to be done in designer before we > can achieve this. Currently Designer knows too much about the Teiid's > configuration, that needs to be fixed such that it only communicates > only through the known public API like JDBC and Admin API. > > Ramesh.. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-261) The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature

by Dan Florian (JIRA)

The Designer Eclipse Feature Should Be Separated Into A Design-Time Feature And A Runtime-Time Feature ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-261 URL: https://jira.jboss.org/jira/browse/TEIIDDES-261 Project: Teiid Designer Issue Type: Task Affects Versions: 7.0 Reporter: Dan Florian Fix For: 7.0 A version of Teiid Designer should be available that does not include the ability to perform data preview, connection management, and VDB execution. This design-time Designer would be suited to users that are strictly data modelers. A "design-time only" Designer would have a reduced footprint over the current Designer. Another Designer that is more suited to users that test models and VDBs would then be needed. We would build this Designer by adding on the data preview, connection management, and VDB execution capabilities to the "design-time only" Designer. Eclipse features are the way that different builds of the Designer can be accomplished. We have done a pretty good job of isolating the data preview, connection management, and VDB execution code into their own Eclipse plugins. The Eclipse plugins that were designed to handle these capabilities are the dqp, dqp.ui, and sqlexplorer plugins. However, there are a few cases of code found in "design-time only" plugins that depend on these data preview, connection management, and VDB execution plugins. These cases will have to be addressed in order to complete this task. Separate JIRAs should be written for these cases as they are found and tied to this JIRA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-410) Merge vdb and dqp plugins

by Barry LaFond (JIRA)

Merge vdb and dqp plugins ------------------------- Key: TEIIDDES-410 URL: https://jira.jboss.org/jira/browse/TEIIDDES-410 Project: Teiid Designer Issue Type: Sub-task Reporter: Barry LaFond Due to the nature of our 7.0 changes and removal of embedded Teiid, its become more apparent we don't need the hassle of separate plugins for VDB and DQP -related code. We should investigate merging these plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2010