Changes between Version 3 and Version 4 of ApertureOSGi


Ignore:
Timestamp:
10/12/05 19:39:32 (19 years ago)
Author:
sauermann
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ApertureOSGi

    v3 v4  
    1313 * All bundle activation code is kept outside of the factory, meaning that the code/bundle jar file is also usable in a non-OSGi application. 
    1414 
     15For Aperture, this means that the project is divided into several bundles: 
     16 
     17 * one bundle with the core engine including the registries and all interfaces 
     18 
     19 * for each ApertureDataSource implementation and crawlers that are related one bundle 
     20 
     21 * for each ApertureExtractor (or several for convenience, like "extractor pack") one bundle 
     22 
     23 
    1524Currenly, Aduna and DFKI think that we should base our code only on pure OSGi code (i.e. org.osgi.*) and not use any other utilities such as the !DependencyManager that's currently used in the Aduna code. Perhaps Herko can tell us more about what we're in for, because we both have hardly any experience with OSGi yet.