[
https://jira.jboss.org/jira/browse/TEIID-558?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-558:
------------------------------------
Since the current behaviour is correct, the problem stems from the nature of the read only
protocol behaviour. So, instead of swallowing the exception a new admin API method
"reloadUDF" has been introduced.
Designer is already places the "FunctionDefinitions.xmi" file in the
"extension" module directories, with this new method, instead of using
"addUDF" and "deleteUDF", which does not work as expected, it should
be modified to "reloadUDF".
Failed to load UDF in Embedded when running with MMROFILE protocol.
-------------------------------------------------------------------
Key: TEIID-558
URL:
https://jira.jboss.org/jira/browse/TEIID-558
Project: Teiid
Issue Type: Bug
Components: Embedded
Affects Versions: 6.0.0
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 6.1.0
When the UDF is added through the Teiid Designer, UDF is added as extension module.
However, since Designer uses MMROFILE protocol, it never deletes the UDF extension file,
thus trying to add a new one, finds a old one in the configuration and fails to add and
aborts the operation.
--
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