Any day except for Friday is ok for me.
I have a feeling that it will be a tough discussion ;-)
What I particularly dislike:
* ActiveContext.associate(Thread thread)
* the concept of the context id
* scopeType as a method param (I would prefer a specific method/class
for each supported scope)
Anyway, if you look at Weld Context Management API [1] you'll find out
that it's pretty powerful but also quite complex. And I don't believe we
will be able to achieve the same level of funcionality with less complex
API (without sacrificing correctness).
Martin
[1]
Somewhen this week in the evening (CEST).
I’ll have a low availability for the following 2 weeks.
LieGrue,
strub
> Am 20.06.2016 um 16:55 schrieb Antoine Sabot-Durand
<antoine(a)sabot-durand.net>:
>
> Hi all,
>
> We launched the idea to organize a meeting regarding John's proposal regarding
CDI-30:
>
https://github.com/cdi-spec/cdi/pull/291
>
> I wasn't available last week (going to a conference) but I am this week.
>
> So what are your favorite slots for this meeting ?
>
> Antoine
> _______________________________________________
> cdi-dev mailing list
> cdi-dev(a)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.
_______________________________________________
cdi-dev mailing list
cdi-dev(a)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.