[teiid-issues] [JBoss JIRA] Commented: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules

[Ramesh Reddy (JIRA)]

    [ https://jira.jboss.org/jira/browse/TEIID-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12528970#action_12528970 ] 

Ramesh Reddy commented on TEIID-1077:
-------------------------------------

1) Connection pooling, property management, deployment package, Local Transaction if the source supports it.

2) JCA or not, we should provide templates in the JOPR to create the connections to the data sources. For relational there are templates already defined by JOPR.

3) User would be using same tools/process to create a data source that is JCA or not (ideally). The fact that the DS is JCA component is only a concern in the deployment. So, there should not be any confusion.

4) Now this is tricky. 
  a) If user already has a JCA DS, all they would need just need to develop is a Translation Layer, that understands the connections from the DS
  b) If they have to define the connection semantics too, then they again have options
       - They can define a JCA based connection. Teiid provides a generic implementation library in the connector api.  User can extend this. This route creation of JOPR templates is easy for configuration.
       - Something else. Here the definition of how this artifact is defined or deployed is unknown and completely user defined. At the same time creation of templates is manual user defined action.  (For the Teiid connectors that fall in this category,  Teiid will need to provide these facilities - these are the ones that are TBD)

> Split all Connector projects to define their "Translator" modules and "Connection" modules
> ------------------------------------------------------------------------------------------
>
>                 Key: TEIID-1077
>                 URL: https://jira.jboss.org/jira/browse/TEIID-1077
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Connector API, JDBC Connector, LDAP Connector, Misc. Connectors, Salesforce Connector, XML Connector
>            Reporter: Ramesh Reddy
>
> Split all the connector projects as follows
> connector-jdbc --> translator-jdbc
> connector-ldap --> translator-ldap/connector-ldap
> connector-loopback -> translator-loopback
> connector-salesforce -> translator-sf/connector-sf (more investigation on this)
> connector-text -> translator-text/connector-text
> connector-xml (file, http, soap) --> TBD ( these will not be jca connectors, alternative methods needs to be investigated)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira