[ https://jira.jboss.org/jira/browse/TEIID-143?page=com.atlassian.jira.plug... ] Greg Haber commented on TEIID-143: ---------------------------------- I'm not very invested in how the process of getting connector bundles and/or their associated jars onto a server works, but I do think it is important that we keep some method of hot-deploying either updated connector type bundles or individual jars. We really need to keep the tasks that would require a full server restart to an absolute minimum. This is because Teiid/JBEDSP servers are often a shared resource between multiple different user populations (each with their own VDB and possibly connector bindings or types) so it is painful to require a full server restart for a change in support of only one VDB. This is even more of an issue when talking about embedded - as we are sharing a JVM with other applications, so the pain of a server restart becomes even greater. Yes, in production this work is all done in maintenance windows, so there it isn't such an issue, but in development (and sometimes also test) environments usually you don't bother with windows. OSGI bundles are hot deployable, so that would be a very suitable approach here. Before going too far down the OSGI path though, please make sure that this won't introduce problems using an embedded Teiid under our sibling project, JBoss App Server - I believe that their OSGI bundle support is still under development. -- 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