Hi, Am Mittwoch, den 30.04.2008, 08:35 +0200 schrieb Carsten Ziegeler: > Felix Meschberger wrote: > > Hi Carsten, > > > > Am Dienstag, den 29.04.2008, 16:51 +0200 schrieb Carsten Ziegeler: > >> I'm wondering why we export the jackrabbit-api in our jcr.api? > >> The jcr api should imho not be tied to any jcr implementation. > > > > You are right, of course and we should move the jackrabbit API another > > bundle, e.g. o.a.s.jcr.jackrabbit.api - in line with > > o.a.s.jcr.jackrabbit.[server|client] > > > > WDYT ? > > > I'm not sure :) Do we need the jackrabbit api at all? We could export it > by both, server and client if we need it somewhere?
I was thinking about this option, too. But it has IMO two drawbacks: (1) It mixes API and implementation and requires two bundles to export things. The more problematic drawback is, that consuming bundles wire to either the client or server bundle when using the Jackrabbit API. When the client and/or server bundle is updated, all these consuming bundles need to be rewired, which could amount to a big load of rewirings. In the case of having a separate API bundle, the update of the client and server bundles would only have an influence on the components using the registered services but not on all wirings. Regards Felix
