Changes between Version 4 and Version 5 of ApertureOSGi


Ignore:
Timestamp:
10/17/05 12:27:09 (19 years ago)
Author:
Herko_ter_Horst
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ApertureOSGi

    v4 v5  
    2323 
    2424Currenly, 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. 
     25 
     26Comments by Herko: 
     27 
     28Ideally, libraries like this should contain no OSGi-specifics whatsoever. I think of OSGi as just one of many possible runtime environments. However, it is beneficial to design the software with OSGi in mind, as the programming model of OSGi (or SOA in general) enforces a clean separation of interface and implementation and loose coupling between modules (bundles). 
     29 
     30Having said that, I see no reason NOT to use the !DependencyManager when using the library in an OSGi context. The !DependencyManager provides support for a number of common scenarios when dealing with interdependent services, in addition to the syntactic dependency managment of the OSGi framework itself.