[MGNLUI-1821] Use JcrNodeAdapter in the message view form Created: 10/Jul/13 Updated: 15/Mar/19 Resolved: 15/Mar/19 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | pulse |
| Affects Version/s: | 5.0, 5.0.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Jozef Chocholacek | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Description |
|
In the message view (a.k.a. message detail) in the Pulse, only the message properties available via getters are accessible, because the BeanItem is passed to the form. As the message is stored as JCR node, the JcrNodeAdapter can be used. But be careful - only read-only, as for modification of messages, the MessagesManager should be used. |
| Comments |
| Comment by Jozef Chocholacek [ 10/Jul/13 ] |
|
Or perhaps it would be enough to update PulseMessagesPresenter.assignPropertiesFromMessage() method to walk through the message.keySet() and create all the missing values. |