[
https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-143:
------------------------------------
The requirements are
1) It must be discoverable, should be able define them without modifications to other
parts of system
2) Prefer to inherit common properties, so that the all connector specific properties can
be defined in one place
3) Should be able to load dependent jars in non-delegating class loader
4) Should be able to define the third party dependencies externally to the artifact (CAF
includes them, but should have option to specify externally, if needed)
5) Preferably single artifact (Like CAF)
The comment above in one solution, where CAF file includes the type information and all
the necessary jars. But this does not satisfy (4). We could additionally support
".cdk" files in a directory along with their dependencies to support the item
(4).
Query should 'find' connector types and jars rather than have
them predefined in the config.
--------------------------------------------------------------------------------------------
Key: TEIID-143
URL:
https://jira.jboss.org/jira/browse/TEIID-143
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Affects Versions: 6.0.0
Reporter: John Doyle
Fix For: 6.1.0
Original Estimate: 1 week
Remaining Estimate: 1 week
Currently, dqp as delived with Designer is preconfigured with connector types. I think
it should discover the connectors that are available upon startup. This would make it
easier to add connectors to a kit. The current process for adding a connector to a kit is
manual and error prone. We have problems with it on nearly every release.
This is also an attractive feature for embedding query in other environments.
--
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