[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Re: RCP, OSGi and all that
- From: Peter Kriens <Peter.Kriens@xxxxxxxx>
- Date: Tue, 9 Nov 2004 10:24:48 +0100
- Delivered-to: firstname.lastname@example.org
- Organization: aQute
OSGi releases must be backward compatible, so as long as developers
stick to R3 features everything should work fine.
It is mandatory in OSGi that unrecognized headers are ignored.
The problem I see is that Eclipse is based on OSGi but does not (yet?)
provide a very OSGi oriented programming model. As with any large
system, it is not realistic to expect that a bundle that uses features
from the Eclipse environment will run unchanged on Knopflerfish.
However, most bundles that are written with this in mind, will run on
both. Actually, it is very likely that most Knopflerfish, or OSCAR,
bundles work perfectly in Eclipse.
>> Also, for this scenario to work, knopplerfish would need to be happy or
>> least tolerant of the extended header definitions from the osgi 4 rfcs
>> eclipse 3 uses.
GN> Eclipse 3.0 extended the OSGi R3 framework. Knopplerfish only currently
GN> supports R3. So to move bundles between the two, it is necessary to stick
GN> to OSGi R3 constructs.
GN> Since Eclipse 3.0, the OSGi standardisation process has moved on and now
GN> the Equinox layering branch is being used to prototype the changes for OSGi
GN> R4 in the Eclipse OSGi implementation. So it won't be possible to move
GN> bundles that use OSGi R4 features between Eclipse and other OSGi
GN> implementations until the Equinox code (or equivalent) has been merged back
GN> into Eclipse. We are targetting this for Eclipse 3.1. Consequently,
GN> Knopplerfix are very unlikely to implement the OSGi extensions in Eclipse
GN> 3.0 since these will not match OSGi R4.
GN> equinox-dev mailing list
Peter Kriens Mob +33633746480
9C, Avenue St. Drézéry Tel +33467542167
34160 Beaulieu, France Tel +15123514821
AOL,Yahoo pkriens ICQ 255570717