Details
-
Bug
-
Resolution: Fixed
-
Medium
-
4.1.2
-
4.01
-
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
- is duplicated by
-
JRASERVER-23512 Undocumented dropped support for built-in OsWorkflow components in JIRA 4.1.2
- Closed
-
JRASERVER-23521 JIRA does not load workflow components (functions, conditions, validators) from the core libraries
- Closed
-
JRASERVER-23991 WARN in logs: ClassNotFound: com.atlassian.jira.event.listeners.cache.IssueCacheListener
- Closed
- is related to
-
JRASERVER-21873 FlushCachesFunction post-function is deprecated and should be removed during upgrade
- Closed
-
JRASERVER-23965 com.atlassian.jira.event.listeners.cache.IssueCacheListener is not removed
- Closed
- causes
-
SCT-3343 Loading...