[teiid-issues] [JBoss JIRA] Commented: (TEIID-143) Query should 'find' connector types and jars rather than have them predefined in the config.

[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ] Larry O'Leary commented on TEIID-143: ------------------------------------- I do see the concern with keeping them in-sync but I can't imagine that it could be that difficult. You have a few options the say I see it: * Directory contents change triggers an extension module scan * Server start-up triggers an extension module scan Extension Module Scan: * Server performs a scan on the directory to get a list of extension names * The list is then compared to already loaded extension modules ** If directory list contains an entry that does not exist in DB extension modules, load the missing extension from the directory ** If directory list contains an entry that already exists in the DB extension modules, use a diff scheme to determine if the extension should be replaced The diff scheme could be a simple file date/time compared to extension module modify date/time. This would require us to use the original modification date and time from the file when an extension is imported. Time zone would also have to be taken into consideration. Alternatively, a hash could be generated on the file as it is imported into the DB. When a file in placed in the extension modules directory that has the same name as an already loaded extension module the hash from the DB is used to compare to the hash of the file to be imported. If they are different then we analyse the file / DB entry further to see if an update is needed. We could also greatly reduce the synchronization issue by moving the file upon successful import to a sub-directory under the extension modules hot/auto-deploy directory. This way if the file is present on more than one server the two servers won't get stuck in a deploy/update tug-of-war in the event that the the two files are actually different. Although the modify date/time scheme would prevent such a problem. -- 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