[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] getservice throws class cast exception
- From: "Alin Dreghiciu" <adreghiciu@xxxxxxxxx>
- Date: Fri, 30 May 2008 10:45:55 +0200
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BlnMGWG3QgmlubL7vrjs0TfFNlwC3Uy06R6Fblz/0cIfmjXpCgHUEelqOzZ2IJ2osFTdqGAyLAyqO/pEdkdQHhB5opZZ9kBb0w28U8THNCKTUzBCZL1iw5KQNHBbMyr6+8f7g6FdFQR+Qi/OUJXa5NfF73UbBKmOiOnRFM6Wkjg=
+1 for having the api as a separated bundle (third in this case)
Neil, you could add an "Best Practices" chapter to your book.
http://www.ops4j.org - New Energy for OSS Communities - Open
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, <njbartlett@xxxxxxxxx> wrote:
> 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.