[
https://issues.jboss.org/browse/TEIIDDES-1146?page=com.atlassian.jira.plu...
]
Dan Florian resolved TEIIDDES-1146.
-----------------------------------
Release Notes Docs Status: Not Required
Resolution: Done
The ModelExtensionAssistant (MEA) API was changed so that the assistant can now be asked
if it supports a certain capability during a certain context (usually a workspace
selection). All MEAs were changed to implement this new method. The MED management dialog
was also changed to use this new API.
There Are Problems Determining If A Model Extension Definition (MED)
Applies To Workspace Selection
---------------------------------------------------------------------------------------------------
Key: TEIIDDES-1146
URL:
https://issues.jboss.org/browse/TEIIDDES-1146
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 7.6
Reporter: Dan Florian
Assignee: Dan Florian
Priority: Blocker
Fix For: 7.6
MED-related actions need to be able to determine if a MED is applicable for their certain
situation. For instance, determining if a MED can be added to a selected model. Currently
the MED only knows the metamodel URI that it extends and what metaclasses it extends. It
does not know anything about model type (physical or virtual). Should the MED also include
the model type? Or should the ModelExtensionAssistant be responsible for determining the
applicability of it's MED given a certain situation.
Here are 2 scenarios that are causing a problem:
1. The Model MED management dialog is not showing for XML Doc models and should be.
2. The REST MED can be added to non-virtual models.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira