anchor.diff:  [source,xml,indent=0,subs="verbatim,quotes"]
   ----
   	<bean id="emailService" class="example.EmailService">
  -		<property name="blackList">
  +		<property name="blockedList">
   			<list>
   				<value>known.spammer@example.org</value>
   				<value>known.hacker@example.org</value>
  
positive.code: 		</property>
  	</bean>
  
  	<bean id="blackListNotifier" class="example.BlackListNotifier">
  		<property name="notificationAddress" value="blacklist@example.org"/>
  	</bean>
  ----
  
  Putting it all together, when the `sendEmail()` method of the `emailService` bean is
  called, if there are any email messages that should be blacklisted, a custom event of type
  `BlackListEvent` is published. The `blackListNotifier` bean is registered as an
  `ApplicationListener` and receives the `BlackListEvent`, at which point it can
  notify appropriate parties.
  
  NOTE: Spring's eventing mechanism is designed for simple communication between Spring beans
  
negative.code: ----
  	@EventListener
  	@Order(42)
  	fun processBlockedListEvent(event: BlockedListEvent) {
  		// notify appropriate parties via notificationAddress...
  	}
  ----
  