[cdi-dev] inheritance of cdi scopes

Reza Rahman reza_rahman at lycos.com
Mon Mar 7 10:24:05 EST 2016


I've already noted this to the JIRA for the issue. If we can we will add it as further clarification. I don't think it's a necessary step to moving forward.

> On Mar 7, 2016, at 10:09 AM, Mark Struberg <struberg at yahoo.de> wrote:
> 
> 
>> Am 07.03.2016 um 14:12 schrieb Romain Manni-Bucau <rmannibucau at gmail.com>:
>> 
>> This is not the point. I'm for getting it done but the spec states the opposite since it ignores not submitting instances completely and it states that submitting ones are not expected to work very clearly in the previous quote (not being deterministic means it doesn't work).
> 
> 
> Romain has a point :/
> It’s not just left out, it seems to be explicitly marked as non-portable. 
> That should be amended in the concurrency-utils spec.
> And even better: it should explicitly be defined that @RequestScoped works.
> Of course I can live with all vendors agree that it should work. Better than nothing.
> 
> LieGrue,
> strub
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.



More information about the cdi-dev mailing list