[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Barry LaFond edited comment on JBDS-2852 at 2/20/14 9:14 AM: ------------------------------------------------------------- Teiid Designer utilizes DTP by: * relying on the Connection Profile data persistence for basic data source properties * DTP's JDBC connection framework for data preview (query execution, SQL Editor and SQL results display) However we've found that to our data sources typically include a finer definition of the source metadata. For instance, * Our JDBC importer is typically used to pull partial or selected tables, views and procedures from within a schema. In Teiid Designer, we persist this additional information within the source model metadata. Ideally additional metadata should probably be persisted with the data source definition. The JDBC CP's do have a simple "filter" option, but overall it's insufficient. * For LDAP, WS, XML and flat file data sources, the DTP CP's are simplistic. Our importers require additional user inputs to set-up/define a useable data source. For these sources, we have yet to persist this additional data. The Teiid Connection import option involves utilizing a deployed data source which Teiid connects to, pulls in the schema defined for that source and converts it into a common Teiid DDL format. This is a DDL dialect tailored to needs of the Teiid runtime metadata. Teiid Designer can then consume the DDL and convert directly to our EMF metamodels. A part of that importer framework *does* provide generic Data Source deployment functionality and it is currently not tied to connection profiles. was (Author: blafond): Teiid Designer utilizes DTP by: * relying on the Connection Profile data persistence for basic data source properties * DTP's JDBC connection framework for data preview (query execution, SQL Editor and SQL results display) However we've found that to our data sources typically include a finer definition of the source metadata. For instance, out JDBC importer is typically used to pull partial or selected tables, views and procedures from within a schema. In Teiid Designer, we persist this additional information within the source model metadata. This additional metadata should probably JDBC sources tyipcally require define a data source * -- 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