[teiid-designer-issues] [JBoss JIRA] Commented: (TEIIDDES-411) Remove VDB Execution Tab in VDB Editor. Add connector selection and name field functionality to VDB Editor Model Summary page.

[ https://jira.jboss.org/browse/TEIIDDES-411?page=com.atlassian.jira.plugin... ] Barry LaFond commented on TEIIDDES-411: --------------------------------------- 1) VDB Editor needs to expose the JNDI name (aka "connection-jndi-name") for editing for the same reason that "translator-name" (see TEIIDDES-462) needs to be editable. Our out of the box Deploy VDB will only work if users can set these properties during VDB Editing in Designer. 2) JNDI name generation and management is being moved to the DQP plugin. All clean-up work for Workspace/Resource events (close, open, delete) will result in stale Teiid Data Sources and DQP will be responsible for keeping these up-to-date. Generating these from within a VDB (i.e. currently SourceElement class) does not make sense with the direction DQP is going. 3) The VDBModelEntry's "source" or "data source" string value does not refer to the same "Data Source" objects that Designer is creating & deleting on Teiid server via createDataSource()/deleteDataSource()/getDataSourceNames(). Teiid Data Sources are constructed and named using the JNDI name. NOTE: I'd like to clean this terminology up if possible? If we have 3 "Data Source" columns in the VDB Editor, do we use: "Source Name" "Translator Name" "JNDI Name"? 4) VDB model and VDBModelEntry, specifically, needs to account for injecting and/or setting JNDI and Translator information during it's construction. Maybe need to look at both "discoverable" ways to create VDBModelEntry's and a direct way. In other words, if DQP is aware of the necessary Connection info when contructing a VDB, then why not just provide a different constructor? -- 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