Re: [cdi-dev] @ThreadScoped?

Sorry for my brevity. Was on a cellphone only. My point is: Context#get(Bean<T>) and Bean<T> only has getScope() which looks like public Class<? extends Annotation> getScope(); Thus having something like @RequestScoped(allowMultithreads=true) public class BlaBlaController {..} would get represented by a Bean<BlaBlaController> which could only return RequestScoped.class. There is simply no way to return the "allowMultithreads=true" information somewhere as we only deal with Classes. The same applies to BeanManager#getContext(): public Context getContext(Class<? extends Annotation> scope); No Annotation but Class, you see? -> Currently there is no way to evaluate an additional attribute on a scope annotation. And thus section 2.4.2 of the CDI specification also clearly states "A scope type must not have any attributes. If a scope type has attributes non-portable behavior results." roger? LieGrue, strub On Sunday, 20 March 2016, 21:12, Romain Manni-Bucau <rmannibucau(a)gmail.com&gt; wrote: