-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Steps to reproduce
- we reference the bean in camunda:class, which does not exist in application context
Actual result:
- BeansException is thrown and it is not processed in code (instead null-check is there)
Expected result:
- The exception is being caught and the class is instantiated by DefaultArtifactFactory
+ test case is missing
Also see comment here:
https://github.com/camunda/camunda-bpm-platform/commit/f78e6d2055d8e0674baa38834f99efc89fc5155b#diff-7bb5d75091c47a0692d9f1da79615ec0R37