[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ] Larry O'Leary commented on TEIID-143: ------------------------------------- Unfortunately I can not speak for all customers but I do know the customers that I have worked with over the years find it a must to hot-deploy connectors. The connector classes and driver classes, or for that matter any connector configuration changes, should be picked up by the connector service when the connector is initialized or created. Even the ability to apply a connector patch is something that is done outside of normal server maintenance in many cases. I really do not see it as an issue to make connector components available system-wide. A connector should be treated much like a VDB. Now, I suppose you can say the same thing about a VDB but it would not make sense to complicate the deployment and configuration of the system by making it a requirement that a VDB and/or Connector must be deployed to each server instance separately unless the mechanism we use gives the option to deploy server wide. I agree that OSGI for our connector packages is ideal but it still will not address the issue of getting these third-party drivers into the class loader. We still we have the obstacle of third-party drivers being external to the OSGI bundle and can't expect our users to create an OSGI bundle that contains the third-party drivers just so they can make the driver available to our OSGI bundled connector. I am not too familiar with JBoss and its clustering capabilities but I always liked the way WebLogic worked. I deploy my J2EE application to a single instance and the other nodes in the cluster would magically inherit the new application. This is much like we do it now but as we use a DB as our lib repository it may appear to complicate things. Fortunately I do not see the DB repository as a complicated piece. I have always thought that we should get rid of it as it is not really needed but if we want to keep it so that we do not have to move the entire synchronization logic into the server then lets at least make a step in the right direction. Why not just use a push/pull scheme for connector, VDB, and extension module artefacts? Basically, I place a file in a special directory of ServerA and ServerA pushes this file to the DB if it does not already exist or updates it if it does exist and needs updating. ServerB will pick up the change immediately because it receives a configuration change event and pulls the file from the DB to its special directory. So, each server will have the same copy of the file in its file system. This prepares you for the possibility that the DB will go away at some point as each server knows how to manage its local instances of resources. The special directory mentioned above is set via a configuration option/property. This way the code that looks for the files can be re-used in the embedded component as well as Designer. -- 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