[
https://issues.apache.org/jira/browse/JCR-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147667#comment-13147667
]
Jukka Zitting commented on JCR-3142:
------------------------------------
+1 to the general approach. Some comments:
* Wouldn't it be nicer to use the whiteboard pattern for servlet registration
[1]? That way we'd avoid the activate/deactivate code and the HttpService
dependency.
* I'm a bit concerned about exporting the entire jackrabbit-webdav API. So far
we haven't made strict backwards compatibility promises beyond jackrabbit-api
and jackrabbit-jcr-commons (where we now explicitly manage the exported OSGi
package versions), and exporting all the o.a.j.webdav packages significantly
increases our public API footprint.
[1]
http://felix.apache.org/site/apache-felix-http-service.html#ApacheFelixHTTPService-UsingtheWhiteboard
> 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
