[ https://issues.jboss.org/browse/TEIIDDES-1165?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1165: ----------------------------------- Summary: MED Editor Overview page should utilize same "Model Class" and "Model Type" combo boxes as the New Metadata Model wizard. (was: MED Editor Properties page should utilize same "Model Class" and "Model Type" combo boxes as the New Metadata Model wizard.) Description: The Overview tab currently presents a metamodel URI combo box, but we've been trying to get away from EMF. The New Model wizard displays only the simple Model Class and Model Type values. We'd of course, limit the Model Classes to Relational, XML Document, Web Services and Function models. Model types would be Source, View and in the case of Function model, "User Defined Function" model type. Without the Model Type selection, which is currently missing, users won't be able to target or limit applying properties to specific model types. The REST extension properties, for instance is only applicable to "View" models. It's MED should include supported Model Types list to include only View + Relational. We probably need to allow a third Relational model type of "BOTH", so an MED wouldn't have to be created for both metamodels? was: The properties tab currently presents a metamodel URI combo box, but we've been trying to get away from EMF. The New Model wizard displays only the simple Model Class and Model Type values. We'd of course, limit the Model Classes to Relational, XML Document, Web Services and Function models. Model types would be Source, View and in the case of Function model, "User Defined Function" model type. Without the Model Type selection, which is currently missing, users won't be able to target or limit applying properties to specific model types. The REST extension properties, for instance is only applicable to "View" models. It's MED should include supported Model Types list to include only View + Relational. We probably need to allow a third Relational model type of "BOTH", so an MED wouldn't have to be created for both metamodels? -- 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

[ https://issues.jboss.org/browse/TEIIDDES-1165?page=com.atlassian.jira.plu... ] Dan Florian commented on TEIIDDES-1165: --------------------------------------- Also for 7.6, changed ModelExtensionRegistryView to use "Model Class" (metamodel name) instead of metamodel URI. Refactored code out of the OverviewEditorPage so that it can be shared by that editor page and the registry view. -- 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