On Wed, Nov 5, 2008 at 4:04 AM, Simon Kitching <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
