anchor.diff:  ** The main use case for this are asynchronous event observers which are executed in separate threads, yet need to have identical context
   ** There are three methods in this interface - `associate()`, `dissociate()` and `close()`
   
  +* http://docs.jboss.org/weld/javadoc/3.0/weld-spi/org/jboss/weld/manager/api/ExecutorServices.html[`org.jboss.weld.manager.api.ExecutorServices`]
  +
  +** One new method - `getTimerExecutor()`
  +** Returns an instance of https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ScheduledExecutorService.html[`ScheduledExecutorService`]
  +** This executor is only required for the timeout feature of asynchronous events
  +** This method has a default implementation returning `null'
  +
   * http://docs.jboss.org/weld/javadoc/3.0/weld-spi/org/jboss/weld/manager/api/WeldManager.html[`org.jboss.weld.manager.api.WeldManager`]
   
   ** Following methods were removed from the SPI:
  
positive.code: 
  *
  `ResourceInjectionServices.resolveResource(InjectionPoint injectionPoint)`
  *
  `ResourceInjectionServices.resolveResource(String jndiName, String mappedName)`
  
  
negative.code: certain information to Weld via the integration SPI. In this Appendix we
  will briefly discuss the steps needed.
  
  If you are upgrading existing Weld integration to work with Weld 3, see
  <<weld_2_to_3_migration>>.
  
  NOTE: If you just want to use managed beans, and not take advantage of
  enterprise services (EE resource injection, CDI injection into EE
  