[teiid-designer-issues] [JBoss JIRA] Updated: (TEIIDDES-450) Implement the concept of a Translator into Teiid Designer

Implement the concept of a Translator into Teiid Designer --------------------------------------------------------- Key: TEIIDDES-450 URL: https://jira.jboss.org/browse/TEIIDDES-450 Project: Teiid Designer Issue Type: Task Components: Editors, Teiid Integration, VDB & Execution, Views Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.1 The Teiid Project has refactored their connection framework to better align their methodology with the AS container and the JON/JOPR community. As a result Designer will change it's connection framework from dealing with Connectors and Connector Types (ala MMX & Teiid Designer 6.0 thru 6.3). In it's place will be the concepts of Translators and Data Sources. The Translators hold the Teiid-specific properties and methods used at run-time to "translate" or transform/adjust any user query through the Teiid engine at run-time. This takes the place of actual Teiid-specific connector type properties. Data Sources are the portion of "Connecton Factories" that only deal with the actual data source connection properties (URL, Username, pwd, Driver class, etc.....) Designer needs to work on modifying the following: 1) Adjusting the "Teiid" View and underlying ExecutionAdmin (aka Connectors View) to display Translators and their instances instead of "Connector Types and their Connector instances". 2) Provide the hooks in the VDB Editor to manage both a "translator-name" and "connection-jndi-name" within each Relational Source Model's "source" element properties. 3) Provide the hooks for auto-binding models to Translators and JNDI Data Sources to simplify Preview Data functionality. 4) Provide the hooks for allowing users to "edit" or "override" any Translator property for each Relational Source model in a VDB. 5) Provide the hooks to search, select and re-use any set of Translator Properties that may exist in any VDB in the Designer workspace.