anchor.diff:  	}
   
   	@Override
  -	public void onBeforeGetContent(Object entity) {
  +	public void onBeforeGetContent(BeforeGetContentEvent event) {
   		...logic to inspect and handle the entity and it's content before it is fetched
   	}
   }
   ----
   ====
  +
   The down-side of this approach is that it does not filter events based on Entity.
   
   ==== Writing an Annotated StoreEventHandler
  
positive.code: 
  * HandleAfterUnsetContent
  
  .Annotated event handler
  ====
  [source, java]
  ----
  
negative.code: ----
  ====
  
  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
  