content API: cleanup
(MAGNOLIA-3015)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.3 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Description |
|
The JCR specification does not support empty properties:
But the content API has both createNodeData() and setNodeData() methods but since they use JCR properties they behave which I consider being wrong:
So there are two solutions possible: A) differentiate the creation and setting
B) drop the explicit creation (as in JCR) I am very much in favor of B) and would like to deprecate all createNodeData() methods |