You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2017/08/01 11:34:00 UTC

[jira] [Created] (JCRVLT-199) Allow mapping some nt:resource nodes to oak:Resource

Robert Munteanu created JCRVLT-199:
--------------------------------------

             Summary: 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)