jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "JackrabbitOsgi" by ThomasMueller
Date Fri, 29 Jan 2010 10:58:33 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "JackrabbitOsgi" page has been changed by ThomasMueller.
http://wiki.apache.org/jackrabbit/JackrabbitOsgi?action=diff&rev1=3&rev2=4

--------------------------------------------------

  
  The problem with dependencies is, that Jackrabbit Core has quite big number of dependencies.
To launch a Jackrabbit repository a number of libraries have been collected and put together.
Some of these libraries are available as OSGi bundles (e.g. the Jackrabbit helper libraries,
the JCR 2.0 API, Derby) and some are not (yet) (e.g. Lucene, Concurrent, Commons Pool, Commons
DBCP). Tika is special in that it will be available as a bundle starting with release 0.6.
  
- The problem with extensibility is, that Jackrabbit Core has not been built with the kind
of modularity in mind as provided by OSGi. This means internal extension API is not properly
separated from internal implementations. This makes it close to impossible to expose the API
as OSGi {{{Export-Package}}} without also requiring to exposing internal packages.
+ The problem with extensibility is, some internal extension APIs of Jackrabbit Core are not
yet separated from internal implementations. One example is the persistence manager interface.
This makes it close to impossible to expose those APIs with OSGi {{{Export-Package}}} without
also requiring to exposing internal packages.
  
  The current approach followed in the [[http://svn.apache.org/repos/asf/jackrabbit/sandbox/jackrabbit2-bundle|Jackrabbit
2 Bundle Sandbox]] is to embed libraries, which are not available as bundles and to not embed
libraries available as bundles.
  

Mime
View raw message