You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/04/14 07:49:00 UTC
[jira] [Resolved] (SLING-2735) Fragment bundle to provide JCR API classes for webapp deployments mode
[ https://issues.apache.org/jira/browse/SLING-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-2735.
-------------------------------------
Resolution: Won't Fix
> Fragment bundle to provide JCR API classes for webapp deployments mode
> ----------------------------------------------------------------------
>
> Key: SLING-2735
> URL: https://issues.apache.org/jira/browse/SLING-2735
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Chetan Mehrotra
> Priority: Minor
> Attachments: org.apache.sling.fragment.jcr-1.0.1-SNAPSHOT-src.zip
>
>
> While deploying a Sling webapp within an App Server it would be helpful to expose the Repository service to applications running outside of OSGi space i.e. other web apps in same server
> To enable that we would need to
> 1. Move the JCR API related classes org.apache.sling.jcr.jcr-wrapper-2.0.0.jar to the server lib directory
> 2. Have a fragment bundle to expose these classes
> 3. Have the JndiRegistrationSupport from org.apache.sling.jcr.registration expose it to JNDI
> So for Step 2 we would require a fragment bundle which matches the export directives from org.apache.sling.jcr.jcr-wrapper-2.0.0.jar
--
This message was sent by Atlassian Jira
(v8.20.10#820010)