[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] getservice throws class cast exception
- From: "Neil Bartlett" <njbartlett@xxxxxxxxx>
- Date: Fri, 30 May 2008 13:23:18 +0100
- 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=mfrlY1uWQBXbvXDpGkMg7fSYQ6tVuZ0x+R8YVmjjzrVaCjyV2RknP5pE7oT0nZDE1EdBz7kWx3wP3hlTWLmqlhZOBs+JtJKGjT36nSH3u/7JqYQ+yN1b1Vdm52h676X5LjhI0BlI3DqeqokOE5GxzsX+ngBuN8tDtO59ZBNL3tU=
Toni made exactly the same comment via my bug tracker!
I agree, I've intended all along to write such a chapter, I just need
to get around to it...
On Fri, May 30, 2008 at 9:45 AM, Alin Dreghiciu <adreghiciu@xxxxxxxxx> wrote:
> +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, <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.
> equinox-dev mailing list