[
https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug...
]
Larry O'Leary commented on TEIID-143:
-------------------------------------
I like the idea of a CAF file containing everything needed for the connector. In the
instances that the driver JARs can not be bundled into the CAF due to licensing issues
then the CAF will still be loaded but unavailable for use. This would be much like
SQuirreL does. If the driver can't be loaded then the driver definition is
"disabled". We already have the concept of extension modules so if I install a
CAF that does not have the needed drivers the default driver classpath will reference the
driver JAR as an extension module and I will need to manually load the driver JAR into the
extension modules.
I would recommend that we support hot-loading of extension modules via a configurable file
system path. CAF(s) could be loaded in the same manner and maybe should be considered
extension modules in themselves.
For example, if I have a set of connector types which are for the DataDirect drivers in a
CAF file without the DataDirect driver JAR(s), I would simply drop the CAF and required
JAR(s) into /application/lib/ext and when I went to define a new connector binding I would
see the new DataDirect specific connector types in the drop-down list.
If on the other hand I installed the CAF file without the required JAR(s), the connector
types wouldn't be visible on the drop-down list because the drivers could not be
loaded. As an advanced configuration option there would be a check-box or a connector
type edit view that would allow me to see all connector types regardless if their drivers
could be loaded as a means of giving me the ability to modify the connector type
configuration to point it to a new JAR or a new driver class.
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