[teiid-dev] Teiid Admin API Access Changes

In prior releases of Teiid, if a user wanted to access Teiid's Admin API, they could get access to this API through JDBC connection. This was a convenience method Teiid had provided. Internally Teiid created a additional connection for admin. With changes coming from management framework and security, even though supporting the above is possible, it does seem right. What if, the developer who has access to a JDBC connection can not have access to the management or vice versa. Keeping this convenience access together under single connection, also adds significant size to the Teiid's client JDBC driver JAR to bundle the management framework. So, we have been thinking to take these apart such that JDBC connection only provides the access to the data side of the engine, where as a separate "admin" connection will provide a management access. It will be still possible for single user to be in the both roles, however they would simply need to make two separate connections to access respective functionality. This would let us package the admin access classes into a separate jar file, so that this jar would only be required by users who are dealing with admin functionality. Please let us know if you have any comments. Thanks. Ramesh..