11:31 a.m.
Teiid engine needs to be exposed as a JCA Connector
---------------------------------------------------
Key: TEIID-862
URL: https://jira.jboss.org/jira/browse/TEIID-862
Project: Teiid
Issue Type: Sub-task
Components: Embedded, Server
Affects Versions: 6.3
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.3
DQPCore, which is the main interface for the Teiid engine must be available as a JCA
source that is capable of engaging multiple other JCA sources in a data integration
solution. This should leverage the "Work Manager" for carrying out any tasks.
--
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:05 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-862) Teiid engine needs to be exposed as a JCA Connector
[
https://jira.jboss.org/jira/browse/TEIID-862?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-862.
--------------------------------
Resolution: Done
Teiid engine is now exposed as another service in JBoss AS rather than a JCA component.
This service still uses the WorkManager to handle thread management. The
"TransactionManager" is also supplied to the service from the JBoss container.
Although, we initially designed this component to be JCA connector, by moving to above
model, we could simplify the thread usage, transaction management, work management
significantly.
Also, there was no explicit way to define the dependencies of this component based on
other services. In MC you can not define service dependencies on to the JEE components.
Having defined as "service", now its dependencies can be managed.
Teiid engine needs to be exposed as a JCA Connector
---------------------------------------------------
Key: TEIID-862
URL: https://jira.jboss.org/jira/browse/TEIID-862
Project: Teiid
Issue Type: Sub-task
Components: Embedded, Server
Affects Versions: 7.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.0
DQPCore, which is the main interface for the Teiid engine must be available as a JCA
source that is capable of engaging multiple other JCA sources in a data integration
solution. This should leverage the "Work Manager" for carrying out any tasks.
--
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
3 p.m.
New subject: [JBoss JIRA] Closed: (TEIID-862) Teiid engine needs to be exposed as a JCA Connector
[
https://jira.jboss.org/browse/TEIID-862?page=com.atlassian.jira.plugin.sy...
]
Steve Hawkins closed TEIID-862.
-------------------------------
Teiid engine needs to be exposed as a JCA Connector
---------------------------------------------------
Key: TEIID-862
URL: https://jira.jboss.org/browse/TEIID-862
Project: Teiid
Issue Type: Sub-task
Components: Embedded, Server
Affects Versions: 7.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.0
DQPCore, which is the main interface for the Teiid engine must be available as a JCA
source that is capable of engaging multiple other JCA sources in a data integration
solution. This should leverage the "Work Manager" for carrying out any tasks.
--
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
5135
days inactive
5393
days old
2 comments
2 participants
participants (2)
-
Ramesh Reddy (JIRA) -
Steve Hawkins (JIRA)