Hi,

Am Mittwoch, den 14.05.2008, 10:42 +0200 schrieb Carsten Ziegeler:
> Felix Meschberger wrote:
> > Hi,
> > 
> > Am Mittwoch, den 14.05.2008, 10:23 +0200 schrieb Carsten Ziegeler:
> >> Hi,
> >>
> >> should we also rename the package from core to engine (and everything 
> >> else)? I think so, but I just wanted to check before doing :)
> > 
> > Yes, I would say so, too.
> > 
> > In addtion: the core (or engine) bundle provides API. Should we create a
> > separate engine-api bundle ? Just thinking loud ;-)
> > 
> Hmm, do we expect different engines? :) I hope not :) So I guess we're 
> fine with one bundle.

No, we don't. But intending to have multiple implementations is only the
traditional - yet very valid and important - reason. In the OSGi context
another reason is proper separation of API and implementation and thus
proper wiring separation: Consider upgrading an implementation in the
case of split api/impl and the case of combined api/impl. In the case of
split bundles, upgrading the impl only causes consumers of services to
be touched. In the case of combined bundles all bundles wiring to the
API are touched !

But I agree, we probably don't need to split...

Regards
Felix

Reply via email to