By "ignore the inheritance hierarchy" I mean you can stop thinking about abstract classes when designing and use always interfaces with defender methods (if your abstract class needs protected fields or methods this won't work though).
Once you've made the design using interfaces instead of abstract classes it will work the same way: previously you could make the child class override the method in the abstract class or use the base method and now you can make the child class implement the defender method or use the default implementation; I see no difference.
Abraham Marín Pérez
Sent from my iPhone
On 29 Aug 2012, at 23:36, Richard Warburton <[address removed]> wrote:
>> You can ignore the inheritance hierarchy and only use the implements hierarchy to mock multiple inheritance with interfaces+defender methods mocking abstract classes.
> You can't ignore the inheritance hierarchy. Any class that implements
> a method with the right signature will be preferred to a default
> method, regardless of how 'close' the interface is compared to the
> class. This is a significant different between the way inheriting
> implementations works between abstract classes and default methods on
> Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
> This message was sent by Richard Warburton ([address removed]) from LJC - London Java Community.
> To learn more about Richard Warburton, visit his/her member profile: http://www.meetup...
> Set my mailing list to email me
> As they are sent
> In one daily email
> Don't send me mailing list messages
> Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]