[
https://issues.apache.org/jira/browse/SLING-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544814#comment-15544814
]
Thomas Mueller commented on SLING-6090:
---------------------------------------
I understand Carstens reason to avoid a direct dependency to Oak (#1).
Detecting the repository type at runtime (#2) also is not optimal.
A new Sling nodetype (#3) sounds like the best option to me, if it is doable.
The implementation might be slightly more complicated than for example #1, but
is there any other disadvantage?
> Avoid using nt:resource while creating file nodes via SlingPostServlet
> ----------------------------------------------------------------------
>
> Key: SLING-6090
> URL: https://issues.apache.org/jira/browse/SLING-6090
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: Servlets Post 2.3.16
>
>
> Currently Sling uses {{nt:resource}} nodetype while creating file nodes in
> {{SlingFileUploadHandler}} and {{StreamedChunk}}.
> As discussed in OAK-4567 and also in best practices at [1] it would be better
> to avoid using a referenceable nodetype and instead use another nodetype like
> {{oak:Resource}}
> Mail thread on DL
> [1]
> https://adapt.to/2016/en/schedule/let_s-run-the-whole-web-on-apache-sling-and-oak-.html
> [2] http://markmail.org/thread/77xvjxtx42euhss4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
