[JBoss JIRA] Created: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules
5:21 p.m.
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
10:14 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules
[
https://jira.jboss.org/jira/browse/TEIID-1077?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIID-1077:
-------------------------------------
rename "connector" to "connection" in above.
- Change translator build to produce the JAR file
- Keep the RAR file for the connection project
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
2:58 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules
[
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
5:41 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules
[
https://jira.jboss.org/jira/browse/TEIID-1077?page=com.atlassian.jira.plu...
]
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
11:02 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules
[
https://jira.jboss.org/jira/browse/TEIID-1077?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIID-1077:
-------------------------------------
Except for the XML connectors all other modules are now separated. We did some
investigations on the XML configurations that will satisfy Teiid's need. It seems all
options are geared toward supporting the Stub generated Web Service modules. Since the
Teiid needs operate in PAYLOAD fashion these will not work.
We are falling back on original plan to use the JCA for XML connections. This gives a
defacto way to configure, templates for connection and deployment framework. Otherwise we
need to invest time in each of these layers.
So, we will remove HTTP and SOAP connectors and introduce a new connector called
"WS", which will handle both HTTP and SOAP using the "Dispatch"
interface. The user should be able configure to use either SOAP or HTTP.
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
4:22 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules
[
https://jira.jboss.org/browse/TEIID-1077?page=com.atlassian.jira.plugin.s...
]
Ramesh Reddy resolved TEIID-1077.
---------------------------------
Assignee: Ramesh Reddy
Fix Version/s: 7.0
Resolution: Done
The "XML" translator is added along with the "connector-ws" connection
factory module for. XML translator can be used with "WS" or "Text"
connection factories. Tested with JBoss Native using couple of simple web service models.
Added few integration tests, more need to be added.
Split all Connector projects to define their "Translator"
modules and "Connection" modules
------------------------------------------------------------------------------------------
Key: TEIID-1077
URL: https://jira.jboss.org/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
Assignee: Ramesh Reddy
Fix For: 7.0
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 a.m.
New subject: [JBoss JIRA] Closed: (TEIID-1077) Split all Connector projects to define their "Translator" modules and "Connection" modules
[
https://jira.jboss.org/browse/TEIID-1077?page=com.atlassian.jira.plugin.s...
]
Steve Hawkins closed TEIID-1077.
--------------------------------
Split all Connector projects to define their "Translator"
modules and "Connection" modules
------------------------------------------------------------------------------------------
Key: TEIID-1077
URL: https://jira.jboss.org/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
Assignee: Ramesh Reddy
Fix For: 7.0
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5764
days inactive
5822
days old
6 comments
3 participants
participants (3)
-
Ken Johnson (JIRA) -
Ramesh Reddy (JIRA)
-
Steve Hawkins (JIRA)