[
https://issues.apache.org/jira/browse/JCRVLT-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109003#comment-16109003
]
Robert Munteanu commented on JCRVLT-199:
----------------------------------------
We don't allow writing under a mount right now so there will be no way to
create references at runtime. However, we can't control what happens at mount
time, when the composite node store is assembled. Thus the idea of validating
references at mount time. We do the same for versionable nodes, only the
problem there is less tricky, as we don't usually find versionable nodes there.
How do you see other consumers of the JCR API being impacted by this change?
> Allow mapping some nt:resource nodes to oak:Resource
> ----------------------------------------------------
>
> Key: JCRVLT-199
> URL: https://issues.apache.org/jira/browse/JCRVLT-199
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Components: Packaging
> Reporter: Robert Munteanu
>
> In a composite setup we don't support referenceable nodes in mounts. Reality
> is though that for a typical Sling-based setup there will be lots of
> nt:resource nodes in /libs and /apps, and that's were we expect to see
> mounts. Since nt:resource is referenceable any mount-time sanity check will
> fail ( see OAK-6505 ) .
> Rather than force adaption of all content packages that write in /libs and
> /apps to use oak:Resource, I would rather suggest a configuration to
> transparently map nt:resource nodes to oak:Resource ones.
> I did not dig into the code yet but I would like to hear what others think
> about this idea before going further. [~tripod] ?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
