-
Task
-
Resolution: Fixed
-
Major
-
5.0.1
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Message has to be able to store additional properties (next to the defined/known ones) if required. It's perfectly fine to use a map for this purpose - but Message must not be a map - e.g. implement the Map interface.
On the one side this requires to implement lots of methods we don't want to offer - on the other side it makes IoC unusable in case you want to inject a message and a map.
Acceptance criteria
- caused by
-
MGNLUI-650 Make the Message class implement the Map<String,Object> interface
- Closed
- is depended upon by
-
MGNLWORKFLOW-104 Allow commenting when rejecting an activation
- Closed
- is related to
-
MGNLUI-1906 Refactor the Message type
- Closed