[
https://jira.jboss.org/jira/browse/TEIID-1077?page=com.atlassian.jira.plu...
]
Ken Johnson commented on TEIID-1077:
------------------------------------
Couple comments/questions:
1. What value does JCA provide for connections for non XA data sources? Does it allow a
non XA source to participate in a container managed transaction?
2. What will the user experience be from a management and configuration perspective if
there are different types of connectors - some JCA and some not? Will they all still be
configured as DS's and appear similarly in the management tree view?
3. The above suggests there will be a jca ldap and text connector/connection.
SF.com is
uncertain and xml is non-JCA. The some-JCA, some-not-JCA approach seems potentially
confusing for users.
4. What is the general guidance for custom connector implementation?
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