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 2010/12/09 18:20:01 UTC

[jira] Updated: (JCR-2608) Making Jackrabbit content repo usable from OSGi

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

Jukka Zitting updated JCR-2608:
-------------------------------

    Summary: Making Jackrabbit content repo usable from OSGi  (was: Making Jackrabbit content repo usable from OSGi (Equinox))

I started drafting an improved Jackrabbit repository bundle in the sandbox area of our svn.

> Making Jackrabbit content repo usable from OSGi
> -----------------------------------------------
>
>                 Key: JCR-2608
>                 URL: https://issues.apache.org/jira/browse/JCR-2608
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-spi-commons
>    Affects Versions: 1.6.1
>         Environment: Ubuntu 10.04, 64-bit, Fuse 4.2 (Equinox-based ServiceMix)
>            Reporter: Samuel Cox
>            Priority: Minor
>
> I have been using home-grown, Jackrabbit OSGi bundles for the past year in Fuse 4.0 (Felix based).  For the most part, I put everything in an uber-bundle represented by jackrabbit-core.  However, the service lookup process used in jackrabbit-spi-commons (META-INF/services) started failing when we moved to Fuse 4.2 (Equinox based).  I have not had time to try your new 2.0 bundles.  Also, I realize this is probably an OSGi-SMX problem as opposed to yours.  I just thought I'd let you know because it looks like you're making an effort to provide bundles.

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