[MGNLHARDLK-66] Support lock for resource app (different from resource legacy) Created: 23/Sep/15 Updated: 01/Oct/18 Resolved: 23/Sep/15 |
|
| Status: | Closed |
| Project: | Project - Telia - Hard Locking (closed) |
| Component/s: | None |
| Affects Version/s: | 0.24 |
| Fix Version/s: | 0.31 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Oanh Thai Hoang | Assignee: | Tran Quang The |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1d 5h | ||
| Original Estimate: | 2d | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Account: | TeliaSonera (TELIA) |
| Epic Link: | Hard Locking |
| Sprint: | Telia - Sprint 12, Telia - Sprint 13 |
| Description |
|
Resource app works different from normal app because it handle contentConnector to work with classpath, file system, jcr. So Lock module will create more class to support lock and unlock for resource-app:
|
| Comments |
| Comment by Oanh Thai Hoang [ 23/Sep/15 ] |
|
Please review in branch |