Details
-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
4.1.2, 4.2
-
4.01
-
Description
OSWorkflow implements several built-in components (functions, conditions, validators) integrating with e.g.:
- JNDI
- EJB
- Beanshell
While most of them is of arguable value, JIRA used to be able to successfully look up and instantiate them. While fixing JRA-20528 a bug was introduced in that JIRA no longer resolves those built-in components. The affected code is in DefaultOSWorkflowConfigurator. As a result, custom workflows using those facilities will face errors that will break their workflows. Note that those components are not used withing default JIRA workflows.
Attachments
Issue Links
- duplicates
-
JRASERVER-22397 DefaultOSWorkflowConfigurator.JiraTypeResolverDelegator should fall back to JiraUtils.loadComponent(objClass) to load the class if type resolver is not found
- Closed
- is related to
-
JRASERVER-23521 JIRA does not load workflow components (functions, conditions, validators) from the core libraries
- Closed