[teiid-issues] [JBoss JIRA] Commented: (TEIID-805) Enable JDBC Connector to provide a way to obtain connection through JNDI
[
https://jira.jboss.org/jira/browse/TEIID-805?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-805:
--------------------------------------
We'll need to have plans around the container transaction/pooling modes that we
support including:
1. Standalone - the current model were we embedded arjuna
2. Fully embedded - where we have no socket transport or at least no inflowing xa
transactions, and we rely on the container's transaction manager/pooling. For this to
work we would need:
a. a synch request work item that stays bound to the user thread.
b. to move the enlist/delist/locking logic out of SynchConnectorWorkItem and into
PooledConnector/ConnectionPool and to just have SynchConnectorWorkItem associate the
transaction/transactioncontext with the thread so that the container's xa handling
will work.
c. create a dummy TransactionServer that will just create transactioncontexts based on
the transaction associated with the thread (relies on a).
3. Hybrid - where we still allow inflow transactions over the socket transport, but rely
on the container's transactionmanager/pooling. The only way I can see this working is
if we are deployed in AS or a stripped down AS and rely on Arjuna being the
TransactionManager. We have a kitting issue here (and with option 2 in AS) with our
embedded Arjuna.
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