[MAGNOLIA-3474] Make mgnl:resource referenceable to support transition to JCR 2.0 Created: 20/Dec/10 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 4.4.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Jan Haderka | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | quickwin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
Magnolia defines mgnl:resource as nt:resource is in turn defined in JCR 1.0 as [nt:resource] > mix:referenceable - jcr:encoding (STRING) - jcr:mimeType (STRING) mandatory - jcr:data (BINARY) mandatory primary - jcr:lastModified (DATE) mandatory IGNORE However JCR 2.0 changes this definition to: [nt:resource] > mix:mimeType, mix:lastModified primaryitem jcr:data - jcr:data (BINARY) mandatory so we need to add mix:referenceable to mgnl:resource explicitly to keep UUIDs on the binary assets. |
| Comments |
| Comment by Tobias Mattsson [ 02/Dec/13 ] |
|
The spec indeed says that nt:resource does not have mix:referenceable, however Jackrabbit has it in its builtin_nodetypes.cnd file. Checked versions 2.2.8 and 2.6.4. I agree we should base on the spec and explicitly add mix:referenceable on mgnl:resource. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |