Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-22397

DefaultOSWorkflowConfigurator.JiraTypeResolverDelegator should fall back to JiraUtils.loadComponent(objClass) to load the class if type resolver is not found

    XMLWordPrintable

Details

    Description

      In DefaultOSWorkflowConfigurator.JiraTypeResolverDelegator, there is a comment for not fallback to JiraUtils:

      If there is no registered TypeResolver for a particular class, then we do not want to fall back to the default object loading implementation as we know it won't be able to be loaded.

      However, the names of some legacy workflow functions, such as FlushCachesFunction are stored in database although they are not defined as workflow module type anymore, which means there won't be a type resolver (which is a PluginTypeResolver linked to the defining workflow module descriptor).

      Thus, these class will fail to load at runtime if not falling back to JiraUtils.loadComponent(). To get around this, one has to go to each transition in each custom workflow and delete the offending deprecated function, and it's quite a big of work to clean up the workflows.

      Attachments

        Issue Links

          Activity

            People

              pleschev Peter Leschev
              awei Alex Wei (DE)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: