+1 for a "best practices" chapter in a "OSGi in practice" book! Just added an issue for that here http://neilbartlett.name/mantis/view.php?id=33 so you can't go away without it ;-)
-------- Original-Nachricht -------- > Datum: Fri, 30 May 2008 10:45:55 +0200 > Von: "Alin Dreghiciu" <[EMAIL PROTECTED]> > An: "Equinox development mailing list" <[email protected]> > Betreff: Re: [equinox-dev] getservice throws class cast exception > +1 for having the api as a separated bundle (third in this case) > Neil, you could add an "Best Practices" chapter to your book. > > -- > Alin Dreghiciu > http://www.ops4j.org - New Energy for OSS Communities - Open > Participation Software. > http://www.qi4j.org - New Energy for Java - Domain Driven Development. > http://malaysia.jayway.net - New Energy for Projects - Great People > working on Great Projects at Great Places > > On Fri, May 30, 2008 at 10:08 AM, <[EMAIL PROTECTED]> wrote: > > Santosh, > > > > I'm glad you got this working but please bear in mind that it is a > > poor design choice to export an interface from the same bundle that > > provides the service, because it does not truly de-couple the consumer > > from the provider, and it makes it much harder for you to update the > > provider bundle as the implementation of the service evolves. So I > > still recommend that you pull the interface into a third bundle. > > > > Regards, > > Neil > _______________________________________________ > equinox-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/equinox-dev _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
