commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <>
Subject Re: [configuration] Interface vs class
Date Wed, 05 Nov 2008 09:30:04 GMT
On Wed, Nov 5, 2008 at 4:04 AM, Simon Kitching <> wrote:
> So the rule would be:
> * the project provides both an interface and an abstract class that
> implements that interface.
> * code that *uses* the API should always use just the interface, ie
> *call* methods via the interface and pass instances around as the
> interface type
> * code that *implements* the API should always subclass the base class.
> The project reserves the right to add methods to the interface, but will
> always provide a concrete default implementation on the abstract
> subclass. Methods will *not* be added to the interface if a sensible
> default implementation cannot be provided.

So, perhaps I can change Proxy to use an interface rather than a
class?  We already have a default implementation based on JDK proxies.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message