[ https://issues.jboss.org/browse/TEIIDDES-908?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-908: ---------------------------------- Description: In order to simplify JDBC import processing by replacing Designer's RelationalModelProcessor with Teiid's processor, the Salesforce Import use-case needs to be simplified by removing the need to have a separate Extension model. TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model. 1) Add "Edit Extended Properties" action and dialog/editor 2) Create a CND (Compact Node Definition) file/string to embed in the model (non-editable) 3) Decorate the model and it's "extended objects" (i.e. tables and columns) to indicate they are "extended" was: In order to simplify JDBC import processing by replacing Designer's RelationalModelProcessor with Teiid's processor, the Salesforce Import use-case needs to be simplified by removing the need to have a separate Extension model. TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-908?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-908: ---------------------------------- Attachment: edit-salesforce-extension-properties-dialog.png -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-908?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-908: --------------------------------------- Created a "Modeling > Edit XXXXX Extended Properties" action and dialog. The action is enabled IF the new extension framework detects that The Action label and dialog title is driven by the extension handler getDisplayName() value. In this first case it's "Salesforce". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-908?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-908: ---------------------------------- Attachment: (was: edit-salesforce-extension-properties-dialog.png) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-908?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-908: ---------------------------------- Attachment: extension-decorations-in-explorer.png screen pic of extension "decoration" in Model Explorer for both "Model" and Objects that are extended. In this case, Tables -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-908?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-908: ---------------------------------- Description: Designer's current Extension Model framework is limiting the ability to be more flexible when modeling and translating metadata through the VDB at runtime and to inject DB-specific metadata (translator) during JDBC Import. There are also drawbacks from having separate extension models (i.e. The Salesforce Import use-case) TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model. 1) Add "Edit Extended Properties" action and dialog/editor 2) Create a CND (Compact Node Definition) file/string to embed in the model (non-editable) 3) Decorate the model and it's "extended objects" (i.e. tables and columns) to indicate they are "extended" was: In order to simplify JDBC import processing by replacing Designer's RelationalModelProcessor with Teiid's processor, the Salesforce Import use-case needs to be simplified by removing the need to have a separate Extension model. TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model. 1) Add "Edit Extended Properties" action and dialog/editor 2) Create a CND (Compact Node Definition) file/string to embed in the model (non-editable) 3) Decorate the model and it's "extended objects" (i.e. tables and columns) to indicate they are "extended" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-908?page=com.atlassian.jira.plug... ] Dan Florian resolved TEIIDDES-908. ---------------------------------- Release Notes Text: Salesforce extension properties for tables and columns are automatically created when the Salesforce importer is run. Those extension properties can now be edited using the Properties View. Resolution: Done Salesforce plugin contributes a Model Extension Definition (MED) file (salesforce.mxd) at startup. This MED defines the Salesforce extension properties. The Salesforce importer uses the MED to add those properties to tables and columns. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira