[MAGNOLIA-3694] Provide Mock-Implementations for JCR-Api (Node, Property etc.) that are independent from Content-API Created: 17/May/11 Updated: 31/Jul/17 Resolved: 01/Jul/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.5 |
| 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 |
|
Before Mgnl 5.0 the Content-API was the "master" - basically all code was relying on it and hence there was proper Mock-Implementations for it. Direct access was the exception so the few available Mock-Implementations for JCR-Types are based on the Content-API. With Mgnl 5.0 (and JCR 2.0) we want to change strategies - use JCR-API where possible. So now we need a full set of Mock-JCR-Implementations - all of them being independant of the Content-API mocks'. These could/should now rely on the JCR-mocks. |