[
https://jira.jboss.org/jira/browse/TEIID-418?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-418:
------------------------------------
Added "metamatrix.extension.CommonClasspath" property and removed
"metamatrix.server.UDFClasspath" property. This new property will serve as
common classpath property that defines the modules from extension modules, which will be
used to load UDF libraries, Membership domains, custom trackers and more importantly
Connector Bindings.
Also added "ConnectorTypeClassPath" to the "Connector" properties.
This classpath defines all the jars required by a given Connector, either Teiid jars or
any third party jars supplied automatically by Teiid when license permits. This path is
defined by Teiid process at kitting time, and should not be modified by the user.
Now, if a user is using the "JDBC Connector", Teiid will not supply any third
party jars like Oracle. However, they have multiple choices how they can add this to Teiid
system. They can
1) Add to the "lib" directory. Requires a restart to pick up the new jar. or
2) Add as extension module, and then add that jar to
"metamatrix.extension.CommonClasspath" property using console or admin api. or
3) Add as extension module, and modify the "ConnectorClasspath" in the connector
binding properties and add jar there (old way)
2 & 3 will not require restart. With the connector class path is resolved as
ConnectorClassPath <---- metamatrix.extension.CommonClasspath <------
ConnectorTypeClassPath
The ones in the left override from right in dependency hierarchy. This way if user adds
"oracle" they have option to throw in "lib" and access it everywhere,
or add it in "common" and access it every where with out modifying the connector
classpath.
Server Extensions should be loaded from a Extension classpath
-------------------------------------------------------------
Key: TEIID-418
URL:
https://jira.jboss.org/jira/browse/TEIID-418
Project: Teiid
Issue Type: Feature Request
Components: Build/Kits, Common, Server
Affects Versions: 6.x
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.1.0
Currently the MembershipDomain, CustomTracker load from libraries which are defined as
part of the boot class path, these need to be loaded from the extension classpath, so that
they can be added or removed without server re-start.
--
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