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

Felix Meschberger updated JCR-2254:
-----------------------------------

    Description: 
To use the JCR API in OSGi frameworks it would make perfect sense to have 
separate OSGi bundles providing the API. For JCR 2.0 the library will come as 
an OSGi bundle. For JCR 1.0 the library is not an OSGi bundle and needs to be 
wrapped.

For this, Jackrabbit should provide a simple wrapper bundle around the JCR 
library and export the respective API.

This wrapper project would be part of the jackrabbit/commons proper and mainly 
be a service of Jackrabbit to the OSGi users out there.

  was:
To use the JCR API in OSGi frameworks it would make perfect sense to have 
separate OSGi bundles providing the API. For JCR 2.0 the library will come as 
an OSGi bundle. For JCR 1 (talking of 1.0.1, actually) the library is not an 
OSGi bundle and needs to be wrapped.

For this, Jackrabbit should provide a simple wrapper bundle around the JCR 
library and export the respective API.

This wrapper project would be part of the jackrabbit/commons proper and mainly 
be a service of Jackrabbit to the OSGi users out there.

        Summary: Create OSGi wrapper for JCR API 1.0 library  (was: Create OSGi 
wrapper for JCR API 1.0.1 library)

Angela just told me that the 1.0.1 library never has been officially released 
due to compatibility issues. Thus lets do the 1.0 bundle...

> Create OSGi wrapper for JCR API 1.0 library
> -------------------------------------------
>
>                 Key: JCR-2254
>                 URL: https://issues.apache.org/jira/browse/JCR-2254
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: JCR API
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> To use the JCR API in OSGi frameworks it would make perfect sense to have 
> separate OSGi bundles providing the API. For JCR 2.0 the library will come as 
> an OSGi bundle. For JCR 1.0 the library is not an OSGi bundle and needs to be 
> wrapped.
> For this, Jackrabbit should provide a simple wrapper bundle around the JCR 
> library and export the respective API.
> This wrapper project would be part of the jackrabbit/commons proper and 
> mainly be a service of Jackrabbit to the OSGi users out there.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to