[ https://issues.apache.org/jira/browse/OAK-9823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus moved JCR-4802 to OAK-9823: ------------------------------------------- Key: OAK-9823 (was: JCR-4802) Workflow: no-reopen-closed (was: no-reopen-closed, patch-avail) Project: Jackrabbit Oak (was: Jackrabbit Content Repository) > Document difference between servlets provided by Jackrabbit legacy, and > Jackrabbit Oak > -------------------------------------------------------------------------------------- > > Key: OAK-9823 > URL: https://issues.apache.org/jira/browse/OAK-9823 > Project: Jackrabbit Oak > Issue Type: Improvement > Reporter: Graham Leggett > Priority: Major > Attachments: oak-run-readme.patch > > > At this time, there is significant confusion over the remoting capabilities > of Jackrabbit. > In Jackrabbit legacy, we have two servlets: > - Simple Webdav Server > - JCR Webdav Server > In Jackrabbit Oak, we have what seems to be a different servlet: > - OakServlet > The confusion comes about because at first pass, the end user gets the > impression that the server in oak-run is the Simple Webdav Server and JCR > Webdav Server from jackrabbit legacy. > Only after deploying the server and start digging into the source to get an > explanation of the behaviour of the oak server, we find the OakServlet, which > appears to contain an undocumented ad-hoc HTTP API, which is in turn hard > coded to accept Basic Authentication only. > https://github.com/apache/jackrabbit-oak/blob/trunk/oak-http/src/main/java/org/apache/jackrabbit/oak/http/OakServlet.java > Ideally the docs for the server part of the oak-run tool needs to be updated > to clearly indicate that the API bears no relation to past APIs, on this page: > https://github.com/apache/jackrabbit-oak/blob/trunk/oak-run/README.md -- This message was sent by Atlassian Jira (v8.20.10#820010)