[MAGNOLIA-5025] Use IoC instead of WorkflowModule.getInstance() Created: 13/May/13  Updated: 14/May/13  Resolved: 14/May/13

Status: Closed
Project: Magnolia
Component/s: activation, workflow
Affects Version/s: None
Fix Version/s: 4.5.9

Type: Bug Priority: Neutral
Reporter: Zdenek Skodik Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File warn.log    
Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

To keep clean logs and prevent feelings that something might be wrong. Find the exception attached.



 Comments   
Comment by Jan Haderka [ 14/May/13 ]

This is a module instance we are talking about. It is a singleton, not just ordinary class for which we can create new instance at whim.
What you should use instead of Components.getComponent(WorkflowModule.class) is Components.getSingleton(ModuleRegistry.class).getModule(WorkflowModule.class)

Generated at Mon Feb 12 04:01:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.