OSGi Zone - Comments for "Eclipse Equinox - Fulfilling the Promise of Write Once Run Anywhere"

I must know it I am the

da152 — Tue, 25 Mar 2008 09:28:46 -0400

I must know it I am the project lead :-)

well spotted Christian!

jsugrue — Tue, 25 Mar 2008 08:31:04 -0400

well spotted Christian!

Hi James, However its Riena

da152 — Tue, 25 Mar 2008 08:12:24 -0400

Hi James,

However its Riena and not Rienna (as in your slide)

thanks

christian

Naturally, as one of the

marrs — Wed, 19 Mar 2008 13:26:47 -0400

Naturally, as one of the people involved in Apache Felix, I might be biased a bit, but stating that Felix is a) too immature and b) has many extra API's added to OSGi in my opinion is not a fair representation of the facts.

In my experience, even though not all of the optional R4.1 features are supported in Felix, more specifically fragments, the core is very stable and mature. In fact, Felix, coming from Oscar, predates Equinox and possibly even Knopflerfish, so it's very stable and mature.

Secondly, Felix does not add extra API's to OSGi. If any of the frameworks do that, it would be Equinox because they need to to support Eclipse and a broad spectrum of RCP applications that rely on them. You can argue if that's good or bad, but the real answer is that "it depends".

Equinox is far away from

rehte — Tue, 18 Mar 2008 05:55:33 -0400

Equinox is far away from perfectness. It even cannot provide a decent DS implementation, which is very important in OSGi R4.1.

IMO, Knopflerfish is the best OSGi implementaion. Felix is too immature and have many extra API added to OSGi API, which conflicts with OSGi's initial purpose.