[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-881) Teiid Designer admin connections should be based on a configurable runtime.
[
https://issues.jboss.org/browse/TEIIDDES-881?page=com.atlassian.jira.plug...
]
Paul Richardson resolved TEIIDDES-881.
--------------------------------------
Resolution: Partially Completed
While an Admin API has not been successfully abstracted, the intention of Designer being
able to work with different Teiid versions has been achieved.
An SPI plugin has been introduced providing generic interfaces that are Teiid version
agnostic as well as an Eclipse extension point.
For support in Designer, the versioned Teiid client runtime is forked and becomes a
submodule, implementing both the SPI interfaces and Eclipse extension point.
Designer picks up the extension in its registry at runtime and selection of the default
server determines which runtime client is used for targeting the modelling, previewing and
deployment.
Teiid Designer admin connections should be based on a configurable
runtime.
---------------------------------------------------------------------------
Key: TEIIDDES-881
URL: https://issues.jboss.org/browse/TEIIDDES-881
Project: Teiid Designer
Issue Type: Sub-task
Components: VDB & Execution
Affects Versions: 7.1.1, 7.2, 7.3
Reporter: John Doyle
Assignee: Paul Richardson
Fix For: 8.1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The admin and preview connections for Teiid Designer rely on paths that specify plugin +
version. Updates to the tooling therefore break existing connections when the version
changes. We should instead rely on a user configurable runtime configuration like other
JBoss runtimes.
--
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