Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: felix-dev@incubator.apache.org
Received-SPF: softfail (herse.apache.org: transitioning domain of
 andre.bottaro@orange-ftgroup.com does not designate 195.101.245.15 as
 permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C76227.26C91D42"
Subject: Backward compatibility
Date: Fri, 9 Mar 2007 09:43:31 +0100
Message-ID: 
 <6CF039C5B32037498B02251E11CDE6B0053F9403@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: Backward compatibility
Thread-Index: AcdiJwQKT3g8hlWOTMWr9gdsRuOsTw==
From: "BOTTARO Andre RD-MAPS-GRE" <andre.bottaro@orange-ftgroup.com>
To: <felix-dev@incubator.apache.org>,
	"OSGi Developer Mail List" <osgi-dev@www2.osgi.org>,
	"OSGi Developer Mail List" <osgi-dev@bundles.osgi.org>,
	<oscar-dev@incubator.apache.org>

------_=_NextPart_001_01C76227.26C91D42
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi,

It happens that more than a year after the 4th public release of =
OSGi(tm) specification and that felix project has begun, there is still =
an important gap to overcome for oscar developers to adopt felix =
platform :=20
- The numerous R3 bundles developed before are not deployable as is on =
the felix platform whereas the Core specification announce that OSGi(tm) =
platfroms must be backward compatible (Manifest version 1 and 2)
- The felix platform is delivered with a bundle repository client which =
is not compatible with previous repositories. It is due to obr 2 =
technical disrupt and felix decision (?) not to remain backward =
compatible.

It explains that the choice between R3 and R4 before any development =
phase is not easy and I admit that I sometimes recommend to stay on the =
good old oscar... (especially for quick developments, quick application =
tests, or developments with existing R3 bundles).

Some (naive ?) solutions may answer the 2 problems I mention. Tell me if =
it is reasonable:
- felix Module Class Loader may enable bundles with manifest version 1 =
to import all the packages of the boot-delegation classpath. Or even =
better, a R3 module class loader can be attached to those bundles.
- oscar bundle repository client may be embedded in the felix one in =
order for the latter to be backward compatible. (on this simpler topic, =
I could recommend using felix with kf bundle repository client and =
server...)

I did not check if other platforms treat R3 bundles better. Was the core =
specification too ambitious ?=20

--
Andr=E9=20

------_=_NextPart_001_01C76227.26C91D42--