[
https://issues.jboss.org/browse/TEIIDDES-2406?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2406:
----------------------------------------
Currently source models maintain "connection" info. This info relates to
connection profile information. We also inject the *translator* type in these properties.
The JNDI name for a source model, however, is currently only defined a VDB and it can be
different for a source model in different VDBs.
So specifying a JNDI name - per - source model is doable, however we'd be setting
precident, or changing our paradigm a little.
So would we want a *Source Connection* panel (via dialog/wizard or view) that would
contain at least 1) Translator type and 2) JNDI name ?
We've also have a JIRA which would make it possible to define Translator Override
instances to be defined outside of a VDB and used for multiple source models, which is
also changing our VDB-centric editing of source model connection info.
Provide option to set JNDI, instead of Connection Profile, in order
to do data preview
--------------------------------------------------------------------------------------
Key: TEIIDDES-2406
URL:
https://issues.jboss.org/browse/TEIIDDES-2406
Project: Teiid Designer
Issue Type: Feature Request
Components: Data Preview
Affects Versions: 8.6
Reporter: Van Halbert
In a collaborative environment, the data sources could already be setup on the server.
So in Designer, when doing data preview, it would user friendly to be able to set the JNDI
reference to use, instead of having to create a connection profile. And that would
eliminate the need to create a new data source in order to preview.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)