You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/08/11 15:52:14 UTC

[jira] Commented: (JCRSITE-19) Create OSGi wrapper for JCR API 1.0 library

    [ https://issues.apache.org/jira/browse/JCRSITE-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741874#action_12741874 ] 

Jukka Zitting commented on JCRSITE-19:
--------------------------------------

OK, I'm fine with the proposed artifactId/version pattern since there's already precedent for that.

> Create OSGi wrapper for JCR API 1.0 library
> -------------------------------------------
>
>                 Key: JCRSITE-19
>                 URL: https://issues.apache.org/jira/browse/JCRSITE-19
>             Project: Jackrabbit Site
>          Issue Type: New Feature
>          Components: wrapper
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: jcr api wrapper 1.0.0.000
>
>         Attachments: jcr-api-project.tgz
>
>
> 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.