Design pattern for default implementation with empty methods

Question

Is there a specific design pattern that describes the scenario where a non-abstract default implementation is provided that implements all or some of the method

Answer 1

I have seen this design used in spring where they have a class named FlowExecutionListenerAdapter which saves you implementing all the FlowExecutionListener operations.

However, it does sound like the Null Object Pattern too. However I feel it sits better in the Adapter world purely because it changing the behavour of the interface by allowing you only to implement the bit you want...but its a tough one.

I'm sure this question has been asked before?

This sounds similar no? might be worth a read.