[
https://issues.apache.org/jira/browse/JCR-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147680#comment-13147680
]
Felix Meschberger commented on JCR-3142:
----------------------------------------
Re whiteboard: Yes, but this causes duplicate configuration to be required: for
the alias (aka Servlet Path) and the prefix path. One solution would be to
overwrite the getInitParameter(String) method to return the "alias" property
value if the prefix path property is requested. Hmm...
Re webdav export: I agree. The options basically are: embed the webdav library
in the jcr-server library (jcr-server probably is closely tied to webdav
anyway) or export from the webdav library.
> Create OSGi Bundles from jackrabbit-webdav and jackrabbit-jcr-server libraries
> ------------------------------------------------------------------------------
>
> Key: JCR-3142
> URL: https://issues.apache.org/jira/browse/JCR-3142
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-jcr-server, jackrabbit-webdav
> Affects Versions: 2.3.2
> Reporter: Felix Meschberger
> Attachments: bundleize-davex.txt
>
>
> Propose to generate bundles from the jackrabbit-webdav (exporting everything)
> and jackrabbit-jcr-server (exporting nothing) libraries. In addition a new
> class is added to the jackrabbit-jcr-server library, which in case of
> deployment in an OSGi framework will register a Servlet with the OSGi
> HttpService to expose the JcrRemotingServlet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
