anchor.diff:  <2> An initializer method must be annotated with `@Inject`. 
   <3> An initializer may accept multiple parameters - each one is an injection point.
   
  -== _Q: You talked about some qualifiers?_
  -
  -A: https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#qualifiers[Qualifiers, window="_blank"] are annotations that help the container to distinguish beans that implement the same type.
  +== You talked about some qualifiers?
  +
  +https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#qualifiers[Qualifiers, window="_blank"] are annotations that help the container to distinguish beans that implement the same type.
   As we already said a bean is assignable to an injection point if it has all the required qualifiers.
   If you declare no qualifier at an injection point the `@Default` qualifier is assumed.
   
  
positive.code: We'll talk about qualifiers later.
  For now, it's enough to know that the bean above is assignable to an injection point of type `Translator` and `java.lang.Object`.
  
  == _Q: Hm, wait a minute. What happens if multiple beans declare the same type?_
  
  A: There is a simple rule: *exactly one bean must be assignable to an injection point, otherwise the build fails*.
  If none is assignable the build fails with `UnsatisfiedResolutionException`.
  If multiple are assignable the build fails with `AmbiguousResolutionException`.
  This is very useful because your application fails fast whenever the container is not able to find an unambiguous dependency for any injection point.
  
negative.code: <2> `javax.enterprise.inject.Instance` extends `Iterable`.
  ====
  
  == Can I use setter and constructor injection?
  
  Yes, you can.
  In fact, in CDI the "setter injection" is superseded by more powerful https://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#initializer_methods[initializer methods, window="_blank"].
  Initializers may accept multiple parameters and don't have to follow the JavaBean naming conventions.
  
  