[JBoss JIRA] Created: (TEIIDDES-905) Replace EMF-based Model Extensions with new framework
by Barry LaFond (JIRA)
Replace EMF-based Model Extensions with new framework
-----------------------------------------------------
Key: TEIIDDES-905
URL: https://issues.jboss.org/browse/TEIIDDES-905
Project: Teiid Designer
Issue Type: Enhancement
Affects Versions: 7.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Blocker
Fix For: 7.4
Designer's current Model Extensions framework has some limitations which include:
1. The current framework allows for only 1 extension model.
2. Extension models are included as a dependent models in VDBs.
3. When sequenced through publishing into the Modeshape repository none of the default "extended" property values are currently sequenced. There is no mechanism in Modeshape to associate 2 or more documents in this way.
4. When using the EMF Extension Model, EMF controls when Annotation objects are created, and we're creating annotation objects even when none are strictly needed (e.g., all the tags in the annotation have default values, and thus don't appear in the XMI file). The result is a lot of unnecessary Annotation objects.
Need to design a new framework that is scalable, allows for applying multiple extensions, includes the extension metadata within a model (initial values and types) and can be easily adapted/sequenced by Modeshape.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (TEIIDDES-1075) Create Model Resource UI Action To Manage Model Model Extension Definitions (MEDs).
by Dan Florian (JIRA)
Create Model Resource UI Action To Manage Model Model Extension Definitions (MEDs).
-----------------------------------------------------------------------------------
Key: TEIIDDES-1075
URL: https://issues.jboss.org/browse/TEIIDDES-1075
Project: Teiid Designer
Issue Type: Sub-task
Components: Modeling
Affects Versions: 7.5
Reporter: Dan Florian
Assignee: Mark Drilling
Fix For: 7.6
Create a model resource context menu action that will provide the user the ability to manage the selected model's stored MEDs. The action should only be enabled when one model is selected and should appear in the "Modeling" submenu. The UI should provide the ability to add to/store those applicable MEDs (i.e., MEDs that extend the same metamodel of the selected model) that are not currently being stored in the model. The UI should also allow the user to remove MEDs from model that are currently stored in the model. Also the UI should:
- provide an option to register any stored, unregistered MED to the registry (just need path from user),
- show a dialog informing the user there are no MEDs saved in the model and none that can be applied based on the model's metamodel URI,
- inform the user when removing a MED that all associated MED model object extension properties will also be deleted, and
- show the user which stored MEDs in model are not registered or if the versions are different
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (TEIIDDES-1073) Create Extension Point And Metamodel Plugin Extensions For Those Metamodels Which Are Allowed To Have Model Extension Properties
by Dan Florian (JIRA)
Create Extension Point And Metamodel Plugin Extensions For Those Metamodels Which Are Allowed To Have Model Extension Properties
---------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1073
URL: https://issues.jboss.org/browse/TEIIDDES-1073
Project: Teiid Designer
Issue Type: Sub-task
Affects Versions: 7.5
Reporter: Dan Florian
Assignee: Mark Drilling
Fix For: 7.6
An extension point should be created in org.teiid.designer.extension that permits metamodel plugins to indicate their metamodel can be extended using the model extension framework. Extensions for each metamodel plugin that can be extended should also be written. This extension point should be loaded by the ExtensionPlugin at startup. The ExtensionPlugin should then register these metamodels with the ModelExtensionRegistry. The registry should add supporting method(s) required by the framework. For instance, when creating or validating a ModelExtensionDefinition (MED), the MED's extended metamodel should be checked to make sure it is authorized to be extended. An existing extension point is used for registering MEDs at startup. This new extension point should be loaded first so that the extended metamodel can be checked when registering/creating the built-in MEDs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months