You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2015/09/01 08:21:46 UTC

[jira] [Updated] (OAK-3185) Port and refactor jackrabbit-webapp module to Oak

     [ https://issues.apache.org/jira/browse/OAK-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amit Jain updated OAK-3185:
---------------------------
    Fix Version/s:     (was: 1.3.5)
                   1.3.6

> Port and refactor jackrabbit-webapp module to Oak 
> --------------------------------------------------
>
>                 Key: OAK-3185
>                 URL: https://issues.apache.org/jira/browse/OAK-3185
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: webapp
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.3.6
>
>
> As mentioned at [1] we should port the jackrabbit-webapp [2] module to Oak and refactor it to run complete Oak stack. Purpose of this module would be to demonstrate
> # How to embed Oak in standalone web applications which are not based on OSGi
> # Configure various aspect of Oak via config
> h3. Proposed Appraoch
> # Copy jackrabbit-webapp to Oak repo under oak-webapp
> # Refactor the repository initialization logic to use Oak Pojosr to configure Repository [3]
> # Bonus configure Felix WebConsole to enable users to see what all OSGi services are exposed and what config options are supported
> This would also enable us to document what all thirdparty dependencies are required for getting Oak to work in such environments
> [1] http://mail-archives.apache.org/mod_mbox/jackrabbit-oak-dev/201508.mbox/%3CCAHCW-mkbpS6qSkgFe1h1anFcD-dYWFrcr9xBWx9dpKaxr91Q3Q%40mail.gmail.com%3E
> [2] https://jackrabbit.apache.org/jcr/components/jackrabbit-web-application.html
> [3] https://github.com/apache/jackrabbit-oak/tree/trunk/oak-pojosr



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)