[MAGNOLIA-4978] Command properties are not initialized Created: 16/Apr/13  Updated: 25/Jun/13  Resolved: 17/Apr/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Bug Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLDATA-177 Revisit commands Closed
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
Release notes required:
Yes

 Description   

Working on MGNLWORKFLOW-46 I've found out that the command properties (in this case 'workflow') are not properly initialised on startup.



 Comments   
Comment by Jozef Chocholacek [ 17/Apr/13 ]

The LaunchWorkflowCommand hadn't been overriding the copy(Command command) method of the Command interface, that's why the workflow property was not used.

We need to check other commands, and override the copy(Command command) method if needed.

Comment by Jozef Chocholacek [ 17/Apr/13 ]

This has to be mentioned in the Commands chapter of the M5 documentation.

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