[MGNLUI-1905] Message must not implement Map Created: 12/Aug/13 Updated: 16/Aug/13 Resolved: 12/Aug/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 5.0.1 |
| Fix Version/s: | 5.0.2, 5.1 |
| Type: | Task | Priority: | Major |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||
| Description |
|
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. |