Create Model Extension Registry Eclipse View
--------------------------------------------
Key: TEIIDDES-1076
URL:
https://issues.jboss.org/browse/TEIIDDES-1076
Project: Teiid Designer
Issue Type: Sub-task
Components: Modeling
Affects Versions: 7.5
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 7.6
Create an Eclipse View that shows the current state of the Model Extension Registry (MER).
The MER is where all Model Extension Definitions (MEDs) and all extendable metamodel
identifiers are stored. Since there will be soon be an Eclipse editor for MEDs this
registry view does not need to show all details of every MED. At a minimum the view should
show for each MED the namespace prefix, namespace URI, metamodel URI, version, if it is
built-in or user-defined, and description. In addition the UI should:
- include a way to add/register a MED to the registry. Users should be able to add a MED
by either (1) selecting existing workspace MXD file (MED must be valid), or (2) selecting
non-workspace MXD file which will add to the file to the workspace and to registry.
- include a way to delete a single MED from the registry (refactor). Ask user if they
also want that MED deleted from all models that are storing it. Warn user the deleting MED
from model will also delete any associated model object properties. Deleting a
user-defined MED from the registry should not automatically delete MXD file from the
workspace unless confirmed by user.
- include a way to open the MED Eclipse editor for a selected model(s). Warn user that
changes can affect models in the workspace. Ask if changes made to MED should be applied
to all models that have been storing that MED (this maybe an MED editor requirement). A
double-click should also open the MED editor.
- include a way to find workspace models storing the single selected MED. Results should
be stored using Eclipse's Search results view.
- should only allow one version of MED in the registry (make sure registry is doing
this)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira