[MGNLUI-5000] Timebox: Assess JCR TreeGrid functionality Created: 05/Feb/19 Updated: 18/Apr/19 Resolved: 22/Feb/19 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.0 |
| Fix Version/s: | 6.1 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1d 1h 29m | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Epic Link: | UI framework: grids and browsing | ||||||||||||||||||||||||||||||||
| Sprint: | Foundation 4, Foundation 5 | ||||||||||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||||||||||
| Description |
|
While implementing the initial version of the TreeView (and to some extend - the ListView), we encountered some problems with using Jackrabbit in Vaadin Grids. In particular - Grid tends to cache items (i.e. Nodes!) within the guts of its DataCommunicator (glue between the client and server-side, manages DataProvider), which occasionally would result into repo exceptions caused by attempts to interact with stale/gone JCR nodes. This might happen e.g. if a Node has been moved around/deleted by another user or by another app. Even Grid's own operations (like inline editing) could cause issues. The current implementation tries to reduce the possibility of such problems, but further assessment/testing needs to be done. What exactly could be done:
|
| Comments |
| Comment by Roman Kovařík [ 19/Feb/19 ] |
|
Test scenarios Inline editing
Renaming
Selection
Deletion
Observation
|
| Comment by Roman Kovařík [ 01/Apr/19 ] |
|
|
| Comment by Maxime Michel [ 16/Apr/19 ] |
|
Can we get a fixVersion for this please? |