anchor.diff:  
   That's not correct and it's important to understand the exact mechanism behind this injection point definition.
   
  -=== Bean vs Bean instances
  +=== Bean vs contextual instances
   
   One of the specific feature in CDI is the fact that all components (qualifiers, beans, producers, etc..) are discovered at deployment time.
   
  
positive.code: 
  
  Another limitation is linked to http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#client_proxies[_client proxies_^].
  In a lot of occasion (interceptor or decorator, passivation, usage of normal scope, possible circularity), the container may need to provide a bean instance wrapped in a proxy.
  For this reason, managed bean classes should be proxyable or the container will raise an exception.
  
  Thus in addition to the above rules the spec also restrictions on managed bean class to support certain services or be in normal scopes.
  
negative.code: }
  ----
  <1> `@Intercepted` is a reserved qualifier to inject the intercepted bean in an interceptor
  <2> here it is used to retrieve the actual class of the contextual instance not the proxy's class implementation may have created
  
  
  
  