[
https://issues.jboss.org/browse/TEIIDDES-165?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-165:
---------------------------------------
When deleting a Scalar Function, the ObjectDeleteCommand results in the dependent
resources (i.e. Virtual Tables and Procedures) being re-validated, which is good, but the
UDFManager doesn't have a chance to de-register the affected Function model before
revalidation. The UDFManager is registered to listen for EObject edit events, but by then
it's too late. The resulting validation is incorrect.
Because ObjectDeleteCommand is in designer.core, there isn't any direct way that
command could tell the UDFManager to perform the library clean-up.
Transformations Dependent On UDF Model Are Not Validated When UDF
Model Changes And Build Is Run
------------------------------------------------------------------------------------------------
Key: TEIIDDES-165
URL:
https://issues.jboss.org/browse/TEIIDDES-165
Project: Teiid Designer
Issue Type: Bug
Components: Modeling, Transformations, Validation
Affects Versions: 6.0.0
Reporter: Dan Florian
Assignee: Barry LaFond
Fix For: 7.5
Attachments: SimpleUDFProjectSet.zip
When you delete a function from the UDF model that is being used by a transformation,
there is no warning dialog saying that another model is dependent on that function. When
you then save the UDF model and a run a build, no validation errors occur indicating a
transformation is using an invalid function. You have to clean the workspace or edit the
model containing the transformation in order to finally get a validation error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira