[
https://jira.jboss.org/jira/browse/TEIID-623?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-623.
----------------------------------
Resolution: Done
changed reloadUDF to extensionModuleChanged(String name) to notify us to purge the
appropriate classloaders and reload the udf model.
Updating Common Extension Classpath With New/Changed UDF JARs Does
Not Make Those JARs Visible Even After A UDF Reload
----------------------------------------------------------------------------------------------------------------------
Key: TEIID-623
URL:
https://jira.jboss.org/jira/browse/TEIID-623
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 6.1.0
Reporter: Dan Florian
Assignee: Steven Hawkins
Priority: Blocker
Fix For: 6.1.0
In Teiid Designer, after a new UDF JAR is added the following code is executed:
EmbeddedAdmin admin = (EmbeddedAdmin)adminConnection.getAdminAPI();
admin.setSystemProperty(DQPEmbeddedProperties.COMMON_EXTENSION_CLASPATH,
buildUDFClasspath());
admin.reloadUDF();
The buildUDFClasspath() method builds an extension jar classpath with just the UDF JARS.
So it would look something like this:
extensionjar:udfjar1.jar;extensionjar:udfjar2
When the Designer tries to query using Teiid embedded that new JAR is not found on the
extension classpath. The reload should pick up the newly added or updated JARS on the
extension classpath.
--
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