[teiid-issues] [JBoss JIRA] Closed: (TEIID-1068) Provide a single Connector, that represents the DS and Teiid Connector for JDBC sources.

[Steve Hawkins (JIRA)]

     [ https://jira.jboss.org/browse/TEIID-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Hawkins closed TEIID-1068.
--------------------------------



> Provide a single Connector, that represents the DS and Teiid Connector for JDBC sources.
> ----------------------------------------------------------------------------------------
>
>                 Key: TEIID-1068
>                 URL: https://jira.jboss.org/browse/TEIID-1068
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: JDBC Connector, Query Engine
>    Affects Versions: 7.0
>         Environment: 7.0 M3
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>            Priority: Critical
>             Fix For: 7.0
>
>
> Currently for dealing with relational databases Teiid requires two separate JCA components. 
> 1. Data source 
> 2. Teiid Connection Factory to the Data Source above
> Teiid query engine talks to 2, which in turn talks to 1. In this scenario, 2 provides the query translation facilities + acts as the proxy connection for the 1. Complications arise, as 2 is  exposed as managed connection as well as 1. To be transactionally correct the both managed connections must behave like one. Also, there is burden on the user to create two separate "-ds.xml" files to define a single Teiid Connector.
> Since for 2, JCA behaviour is not needed, this can be removed. 
> Provide a way to define a single "-ds.xml" file that will create a data source as well as the connection factory. Make the connection factory a stateful connection, which holds on to the data source connection.  Provide templates to create such CF + DS in single step.

-- 
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