[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Re: [osgi-dev] Interoperability problems...
- From: Jim Colson <jccolson@xxxxxxxxxx>
- Date: Wed, 21 Mar 2007 09:15:03 -0500
- Delivered-to: firstname.lastname@example.org
I am confused by this question.... Please clarify...
A bundle that is implementing an OSGi service and wants to claim
compatibility with the spec, needs to run the compatibiltiy kit.
A bundle that implments some service "on top of" an OSGi spec has no OSGi
"compatibility" opportunity, as there is no OSGi spec to be compatiblie
with. Hence, there is no need for an RI, but simply an implementation of
a "compatibile" runtime (e.g. Equinox).
What am I missing here?
Jim Colson, Chief Architect - IBM Client Software
IBM Academy of Technology
Board Member - IT Architect Certification
11501 Burnet Rd. Austin, TX 78758
Ph 512-823-7357, Fax 512-838-0962
Admin: Christine Willis 512-838-3667
Sent by: "OSGi Developer Mail List"
03/21/2007 09:07 [equinox-dev] Re: [osgi-dev]
AM Interoperability problems...
Please respond to
This is a subtle point which I had missed the importance of until now. It
implies that all OSGi developers, if they wish to ensure their bundles are
strictly compliant, must test against the RI downloaded from the OSGi
Alliance. In particular, a bundle tested against a copy of Equinox
downloaded from eclipse.org cannot necessarily be assumed to be compliant.
In light of this, could somebody tell me where on the OSGi Alliance
website (OUTSIDE the member area) I can download the RI?
> The RI shipped by the OSGi Alliance is configured to be a strict OSGi
> Framework. To launch the official RI from OSGi you must follow the
> instructions provided by the OSGi Alliance. That will give you a strict
> OSGi Framework. Changing Equinox to default to a strict OSGi Framework
> and then force Eclipse to configure it for its needs will cause issues
> all Eclipse clients and applications. All of the Eclipse
> clients/applications will have to be reconfigured when they are upgraded
> to the latest Equinox that is now strict. That is something I'm sure the
> Eclipse community would not enjoy.
equinox-dev mailing list