[
https://issues.jboss.org/browse/TEIIDDES-472?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-472:
---------------------------------------
Additional issues that need discussion and resolution....
* If a Source model in VDB is MULTI-SOURCE how do we handle the synchronize() logic that
is trying to keep the "translator" properties in sync with model in workspace.
** (See VdbModelEntry.synchronizeModelEntry() method)
* When a user changes a source model from MULTI-SOURCE to single source, what do we do
with the "extra" source entries?
** Will VDB deployment fail if MULTI-SOURCE == FALSE and more than one <source/>
element is present?
** Assume the first one wins and delete the rest?
** Create VDB validation warnings/errors?
Support multi-source bindings
-----------------------------
Key: TEIIDDES-472
URL:
https://issues.jboss.org/browse/TEIIDDES-472
Project: Teiid Designer
Issue Type: Feature Request
Components: Modeling
Affects Versions: 6.3
Reporter: John Verhaeg
Assignee: Barry LaFond
Fix For: 8.1
Probably need a framework somewhat similar to data roles, but at a model level, to manage
these bindings such that they can be validated against or selected when editing a
transformation.
The VDB and its editor then need to be modified to support capturing this information and
tying it to appropriate translators and JNDI names.
--
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