[teiid-issues] [JBoss JIRA] Resolved: (TEIID-805) Enable JDBC Connector to provide a way to obtain connection through JNDI

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy resolved TEIID-805.
--------------------------------

    Resolution: Done


One thing you do not need is the Teiid's connection pooling, so disable that by providing the "ConnectionPoolEnabled" property.

        <Connector Name="Books Connector" ComponentType="Oracle Connector">
            <Properties>
                <Property Name="ConnectionSource">JNDI:Books</Property>
                <Property Name="ConnectionPoolEnabled">false</Property>
                <Property Name="DeployedName">Books Connector</Property>
            </Properties>
        </Connector> 

This setup is good for any "read only" operations. For insert/update/delete operations Teiid typically needs a XA resource. Although the Data source can be configured as the XA resource there are currently some complications in using that.

The internals of Teiid are written to be expecting a embedding a Transaction Manager than using a supplied Transaction Manager. So, typically Teiid is managing all the resource enlists and delists of the XA resources. Also, the threading model is different than that of a Container. This needs be re-factored to make use of container based Transaction Manager and delegate the calls resource enlistment to Container. 6.3 work might dictate some this work, so we will do more work in this once that direction is set.

> Enable JDBC Connector to provide a way to obtain connection through JNDI
> ------------------------------------------------------------------------
>
>                 Key: TEIID-805
>                 URL: https://jira.jboss.org/jira/browse/TEIID-805
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: JDBC Connector
>    Affects Versions: 6.2.0
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>             Fix For: 6.2.0
>
>
> When Teiid is deployed in "embedded" profile under JBoss AS or Glassfish etc, it would be nice if the Data Source information can be obtained from container to used with Connector Binding for VDB. This will some times eliminates the providing the connection information in duplication, and also keeps the developers with configuring what they already know.
> This is going to experimental feature, as we think there may be some connection pooling, thread context issues with transactions etc.
> The prosed way to configure this will be providing the following property in the Connector Binding properties
>         <Connector Name="Books Connector" ComponentType="Oracle Connector">
>             <Properties>
>                 <Property Name="ConnectionSource">JNDI:Books</Property>
>                 <Property Name="DeployedName">Books Connector</Property>                
>             </Properties>
>         </Connector>
> Traditionally "ConnectionSource" is used to define a class name that is responsible to make the connection like Driver, Data Source class names, here the definition will be expanded to accommodate JNDI look up when the value of this property starts with "JNDI:" 
> If there are better alternative solutions please comment.

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