Uploaded image for project: 'Teiid Designer'
  1. Teiid Designer
  2. TEIIDDES-1225

'Add MED to Registry' action allows attempt to add an invalid MED to the registry

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.7
    • 7.7
    • Extension Framework
    • None
    • Hide

      1) In designer, set 'Build Automatically' off.
      2) Create a new MED in the workspace with a valid prefix and URI. The MED will get created, but has one error in the editor since no properties have been defined.
      3) Use the Editors 'Add to Registry' action. The add will fail, directing you to look at the problem log for the exception.
      We should catch the error before attempting the add, and display the user-friendly dialog.

      Show
      1) In designer, set 'Build Automatically' off. 2) Create a new MED in the workspace with a valid prefix and URI. The MED will get created, but has one error in the editor since no properties have been defined. 3) Use the Editors 'Add to Registry' action. The add will fail, directing you to look at the problem log for the exception. We should catch the error before attempting the add, and display the user-friendly dialog.
    • It is no longer possible to try and add/update a *.mxd file with errors to the registry.
    • Documented as Resolved Issue

    Description

      The 'Add MED to Registry' action looks at the mxd problem markers before doing the add operation. However, if the workspace has not been built the file may not have a problem marker. This results in attempt to add an invalid MED to the registry. We should not allow the process to get that far - ensure the build is complete or check for errors in a different manner.

      Example usage is in ModelExtensionDefinitionEditor.createActions, which uses RegistryDeploymentValidator.checkProblemMarkers to do this check currently.

      Attachments

        Activity

          People

            dflorian@redhat.com Daniel Florian (Inactive)
            mdrillin1@redhat.com Mark Drilling (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: