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

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

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

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/JCRVLT-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110000#comment-16110000 ]

Tobias Bocanegra commented on JCRVLT-199:
-----------------------------------------

what i mean is, the workflow models are versioned and the frozen nodes of the models are used. so if the workflows models are stored in libs, then the mounted space needs to have its own version store.

i understand that the space is r/o, but you still could have references into to spaces. of course it might be possible to somehow map the nodetypes during import. the problem will be to instrument this in the right place.

otoh, the ultimate goal is to drive the r/o store directly from the packages, by loading everything into memory on startup. so the 'driver' could specify the mapping there.

i'll look into a way of providing a nodetype mapping, especially when creating nt:files, which anyways have nt:unstructured jcr:content nodes in jackrabbit.

> 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)
Loading...