July 2010 - teiid-designer-issues

[JBoss JIRA] Resolved: (TEIIDDES-394) Association between a model and a connector binding for use by the Preview functionality should be stored within the model

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-394?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-394. ----------------------------------- Resolution: Done This has been done via other JIRA's required to wire-up COnnection Profiles and models. Basically we're storing CP into in model (except pwd) and using it to discover translator types and to help create data sources in Teiid during Preview Data action. > Association between a model and a connector binding for use by the Preview functionality should be stored within the model > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-394 > URL: https://jira.jboss.org/browse/TEIIDDES-394 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Environment: Designer 5.5.3 > Reporter: Greg Haber > Assignee: Barry LaFond > Priority: Minor > Fix For: No Future > > > The proposal here is that a weak association between a model and the connector binding it is associated with for design time preview functionality should be stored in the model file itself, and used to re-establish the association for preview functionality when that model is brought into Designer (such as when an import of a Model Project Set is performed). > The association would be stored in the model with a minimum of information (just the binding name), and the proposed logic is that if there is already an existing binding in Designer with name matching that in the model file, the association for Preview will be automatically established with that binding. > I have attached an e-mail thread between me and rreddy on this topic. > One wrinkle here (not explicitly discussed in the e-mail thread) is if the referenced binding in the model does not previously exist in the Designer workspace, but _is_ defined by a VDB contained in the same model project set, and feature JBEDSP-287 is implemented (so that such VDB binding definitions do get brought in during import). It would be good if the association for Preview functionality between model and binding could also be re-established in this case. This would presumably require that the import of a model project set first import any VDBs before it imported design time models. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-81) Importing a VDB into the Designer should add the Connector bindings to the Configuration Manager

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-81?page=com.atlassian.jira.plugin.... ] Barry LaFond closed TEIIDDES-81. -------------------------------- Assignee: Barry LaFond Resolution: Done Connection framework from MMX and pre 7.0 is obsolete > Importing a VDB into the Designer should add the Connector bindings to the Configuration Manager > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-81 > URL: https://jira.jboss.org/browse/TEIIDDES-81 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 6.0.0 > Environment: Enterprise Designer in Linux and Windows > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: Future > > > If you bring an existing VDB with Connector bindings assigned into the Designer, those bindings are never added to the Configuration Manager. They appear as if they are there when you look at the Execute screen but they are not and you have to create new. This will be very confusing for any evaluation customers that we are sending the training materials with existing vdbs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-121) Simplify Adding Connector Jar as UDF jar in UDF view

by Barry LaFond (JIRA)

Simplify Adding Connector Jar as UDF jar in UDF view ---------------------------------------------------- Key: TEIIDDES-121 URL: https://jira.jboss.org/jira/browse/TEIIDDES-121 Project: Teiid Designer Issue Type: Feature Request Components: Views Affects Versions: 6.1.0 Reporter: Barry LaFond Priority: Minor Fix For: 6.1.0 Current UDF view provides two actions: Import UDF Extension Jars & Add Connector Jars to UDF The second action is somewhat redundant. Request moving the functionality of the second action into an "Advanced" section of the dialog from the first action. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-93) Designer: ConnectorBindings panel - Combine import action icons into one

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-93?page=com.atlassian.jira.plugin.... ] Barry LaFond closed TEIIDDES-93. -------------------------------- Assignee: Barry LaFond Resolution: Out of Date Connectors View obsolete > Designer: ConnectorBindings panel - Combine import action icons into one > ------------------------------------------------------------------------- > > Key: TEIIDDES-93 > URL: https://jira.jboss.org/browse/TEIIDDES-93 > Project: Teiid Designer > Issue Type: Feature Request > Components: Views > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Assignee: Barry LaFond > Priority: Minor > Fix For: Future > > > Implementation for 5.5.3 release has two separate import actions on the connector bindings panel. Request is to combine the 2 actions into a single action that can access either type of import. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-105) Connector Bindings: Show advanced properties not working in Properties editor of Designer Perspective

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-105?page=com.atlassian.jira.plugin... ] Barry LaFond closed TEIIDDES-105. --------------------------------- Assignee: Barry LaFond Resolution: Done Connectors View obsolute > Connector Bindings: Show advanced properties not working in Properties editor of Designer Perspective > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-105 > URL: https://jira.jboss.org/browse/TEIIDDES-105 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 6.0.0 > Environment: Designer 553 on RHEL > Reporter: Ken Johnson > Assignee: Barry LaFond > Priority: Minor > Fix For: Future > > > When displaying connector bindings in the Properties editor in the Designer perspective, the Show Advanced properties controls (toolbar button and menu pick checkbox) do not enable display of Advanced Properties. The connector binding must be edited in a popup window to access advanced properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-92) Designer: Export / Import of a ModelProject set should carry along the connector binding info.

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-92?page=com.atlassian.jira.plugin.... ] Barry LaFond closed TEIIDDES-92. -------------------------------- Assignee: Barry LaFond Resolution: Done Connectors framework totally re-written. Connection Profile into now stored in Model (if applied) > Designer: Export / Import of a ModelProject set should carry along the connector binding info. > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-92 > URL: https://jira.jboss.org/browse/TEIIDDES-92 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Assignee: Barry LaFond > Priority: Minor > Fix For: Future > > > This is a request resulting from the preview Query development work. Export of a ModelProject set should carry along the connector binding info, so that when it is reImported the bindings are also imported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-174) Closing Project does not hide project-specific source bindings in Connectors View

by Barry LaFond (JIRA)

Closing Project does not hide project-specific source bindings in Connectors View --------------------------------------------------------------------------------- Key: TEIIDDES-174 URL: https://jira.jboss.org/jira/browse/TEIIDDES-174 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Minor Fix For: Future 1) Import Books or Parts and verify Connectors and Source Binding is created in Connectors View 2) Right-click Project and "Close Project" 3) Source bindings still visible (should be removed) 4) Select/deselect the "Hide Connectors Types" button on Connectors view toolbar 5) Sources bindings are now hidden. 6) Re-open project and Source bindings now visible Problem with refresh on Connectors View during Project Close action. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-219) SFDC importer plugin has copies of lots of 3rd party jars that maybe should be in sep plugins

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-219?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-219: ---------------------------------- Assignee: John Doyle Fix Version/s: 7.2 (was: 7.1) > SFDC importer plugin has copies of lots of 3rd party jars that maybe should be in sep plugins > --------------------------------------------------------------------------------------------- > > Key: TEIIDDES-219 > URL: https://jira.jboss.org/browse/TEIIDDES-219 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Documentation, Import/Export > Affects Versions: 6.0.0 > Environment: Designer 5.5.3 MS1 build > Reporter: Greg Haber > Assignee: John Doyle > Priority: Minor > Fix For: 7.2 > > > I noticed that as of MS1, the SFDC importer plugin contains a lot of copies of third party jars, most Apache Axis/Apache Commons stuff. In many cases, these same jars are also in the com.metamatrix.modeler.dqp_5.5.3 plugin since they are also needed by the SFDC connector. I also noticed that some of our other Designer plugins that use external jars put those jars in their own plugins, and import the plugin, rather than putting them in the same plugin as our own code. > We should consider pulling these jars out of the SFDC importer plugin and putting them in their own plugins (which the SFDC importer plugin can then import), or simply importing them in the SFDC importer plugin from the DQP plugin. > The same problem exists to a much lesser degree in the WSDL importer (just the commons-codec-1.2.jar is duplicated in that one). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-276) improve WSDL importer accuracy

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-276?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-276: ---------------------------------- Fix Version/s: Future (was: 7.1) > improve WSDL importer accuracy > ------------------------------- > > Key: TEIIDDES-276 > URL: https://jira.jboss.org/browse/TEIIDDES-276 > Project: Teiid Designer > Issue Type: Task > Components: Import/Export > Reporter: Marc Shirley > Fix For: Future > > > are we trying to do too much ourselves instead of leveraging some standard open source components - seems like somebody must have solved the problem of turn WSDL into accurate Java object heirarchy, and we can go from there... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-239) CLONE -Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-239?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-239: ---------------------------------- Fix Version/s: 8.0 (was: 7.1) > CLONE -Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names > -------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-239 > URL: https://jira.jboss.org/browse/TEIIDDES-239 > Project: Teiid Designer > Issue Type: Feature Request > Affects Versions: 6.1.0, 6.2.0 > Reporter: Michael Walker > Priority: Minor > Fix For: 8.0 > > > This problem occurs in our transformation editor, and also occurs with real-time queries (e.g. from QueryBuilder/SQLExplorer, or any client). > If you reference a non-qualified table name, e.g. "myTable", in a query, we'll attempt to resolve it if it is a unique name. > Strangely, we don't do the same thing for virtual procedures, even if they are unique. Instead, you must use the fully-qualified name. There should be no disparity. This is a usability defect. > This also happens to greatly extend the size of virtual procedure code, making it harder to read and debug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2010