anchor.diff:  ----
   ====
   
  -The type of events you are interested in is determined from the type of the first
  - parameter of each annotated method.
  +These handlers will be called only when the event originates from a matching entity.
  +
  +As with the ApplicationListener event handler in some cases it is useful to handle the event.  For example, when Store
  +methods returns results to the caller.
  +
  +.Event-based annotated event handler
  +====
  +[source, java]
  +----
  +@StoreEventHandler
  +public class ExampleAnnotatedEventListener {
  +
  +	@HandleAfterSetContent
  +	public void handleAfterGetResource(AfterGetResourceEvent event) {
  +		SopDocument doc = event.getSource();
  +		Resource resourceToBeReturned = event.getResult();
  +		...code that manipulates the resource being returned...
  +	}
  +}
  +----
  +====
   
   To register your event handler, either mark the class with one of Spring’s @Component
   stereotypes so it can be picked up by @SpringBootApplication or @ComponentScan. Or
  
positive.code: ==== Writing an ApplicationListener
  
  If you wish to extend Spring Content's functionality you can subclass the abstract class `AbstractStoreEventListener` and
  override the methods that you are interested in.  When events occur Spring Content will call the appropriate methods on
  all instances of `AbstractStoreEventListener`.
  
  .AbstractContentRepositoryEventListener
  ====
  [source, java]
  ----
  
negative.code: 
  * HandleAfterUnsetContent
  
  .Entity-based annotated event handler
  ====
  [source, java]
  ----
  