Designer requires a more flexible Model Object Refactoring framework to handle pre and post transaction events.

The current modeling/editing event and transaction framework in Designer cannot satisfy the requirements to perform certain cross-metamodel clean-up.

In particular, if a user Deletes 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 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.

So I propose an to expand the current "refactorModelHandler" extension point to handle this processing.

The current "RefactorModelExtensionManager" should be renamed to "RefactorModelManager"

Methods should be added such as:

preProcess(int type, Object[] objects) (Where type = DELETE, RENAME, MOVE, ADD)
postProcess(int type, Object[] objects) (Where type = DELETE, RENAME, MOVE, ADD)

Objects could be be Models, Files or EObjects