I just went through the PR one more time. It seems like these are the areas of open discussion still: - The name of the class "ActiveContext" needs to be decided. I'm in agreement its a bad name, but switching to past tense doesn't help IMHO. - Disassociating the thread model and the context model. This is the first change that supports this initiative, so I'm not sure if there are any concerns with that change. - The fact that contexts have IDs. To me it makes sense, but it seems like this is not generally agreed (we need some unique identifier to

sure we can bridge from existing) John On Tue, Jun 21, 2016 at 10:27 AM Martin Kouba <mkouba(a)redhat.com&gt; wrote: > I'm on PTO until Jun 29 :-( > > However, we've already discussed this with Antoine so I think my > presence is not required. > > Martin > > Dne 21.6.2016 v 16:23 John D. Ament napsal(a): > > Unfortunately, my schedule's turned south this week and Friday as of

> > is the only day I have open. > > > > What about next week? Monday? > > > > John > > > > On Tue, Jun 21, 2016 at 4:42 AM Martin Kouba <mkouba(a)redhat.com > > <mailto:mkouba@redhat.com>> wrote: > > > > 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

> 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] > > >

> > > > > > Dne 21.6.2016 v 09:22 Mark Struberg napsal(a): > > > 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 <mailto:antoine@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 <mailto:cdi-dev@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 <mailto:cdi-dev@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. > > > > > > > -- > > Martin Kouba > > Software Engineer > > Red Hat, Czech Republic > > _______________________________________________ > > cdi-dev mailing list > > cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org> > > https://lists.jboss.org/mailman/listinfo/cdi-dev > > > > Note that for all code provided on this list, the provider

> > 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. > > > > -- > Martin Kouba > Software Engineer > Red Hat, Czech Republic >

So choices are Friday 24th 5:00 pm CET (same timeslot than our weekly meeting) or Monday 27th 5:00pm CET. I can do both but prefer Monday. What is your choice? Antoine Le mar. 21 juin 2016 ? 16:35, John D. Ament <john.d.ament(a)gmail.com&gt; a ?crit : > I just went through the PR one more time. It seems like these are the > areas of open discussion still: > > - The name of the class "ActiveContext" needs to be decided. I'm in > agreement its a bad name, but switching to past tense doesn't help

> - Disassociating the thread model and the context model. This is the > first change that supports this initiative, so I'm not sure if there

> any concerns with that change. > - The fact that contexts have IDs. To me it makes sense, but it seems > like this is not generally agreed (we need some unique identifier to

> sure we can bridge from existing) > > John > > > On Tue, Jun 21, 2016 at 10:27 AM Martin Kouba <mkouba(a)redhat.com&gt;

> >> I'm on PTO until Jun 29 :-( >> >> However, we've already discussed this with Antoine so I think my >> presence is not required. >> >> Martin >> >> Dne 21.6.2016 v 16:23 John D. Ament napsal(a): >> > Unfortunately, my schedule's turned south this week and Friday as of >> now >> > is the only day I have open. >> > >> > What about next week? Monday? >> > >> > John >> > >> > On Tue, Jun 21, 2016 at 4:42 AM Martin Kouba <mkouba(a)redhat.com >> > <mailto:mkouba@redhat.com>> wrote: >> > >> > 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

>> 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] >> > >>

>> > >> > >> > Dne 21.6.2016 v 09:22 Mark Struberg napsal(a): >> > > 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 <mailto:antoine@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

>> > this week. >> > >> >> > >> So what are your favorite slots for this meeting ? >> > >> >> > >> Antoine >> > >> _______________________________________________ >> > >> cdi-dev mailing list >> > >> cdi-dev(a)lists.jboss.org <mailto:cdi-dev@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 <mailto:cdi-dev@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. >> > > >> > >> > -- >> > Martin Kouba >> > Software Engineer >> > Red Hat, Czech Republic >> > _______________________________________________ >> > cdi-dev mailing list >> > cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org> >> > https://lists.jboss.org/mailman/listinfo/cdi-dev >> > >> > Note that for all code provided on this list, the provider

>> > 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. >> > >> >> -- >> Martin Kouba >> Software Engineer >> Red Hat, Czech Republic >> >

If we're going to do Friday, I need to know by EOD (business) CET tomorrow. John On Tue, Jun 21, 2016 at 12:23 PM Emily Jiang <EMIJIANG(a)uk.ibm.com&gt; wrote: > I can do Friday but not Monday. In the meanwhile, I'll go through the > code changes to add any comments I have. > > Many thanks, > Emily > =========================== > Emily Jiang > WebSphere Application Server, CDI Development Lead > > MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN > Phone: +44 (0)1962 816278 Internal: 246278 > > Email: emijiang(a)uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM@IBMGB > > > > > From: Werner Keil <werner.keil(a)gmail.com&gt; > To: cdi-dev <cdi-dev(a)lists.jboss.org&gt;, > Date: 21/06/2016 16:33 > Subject: Re: [cdi-dev] CDI-30 hangout meeting > Sent by: cdi-dev-bounces(a)lists.jboss.org > ------------------------------ > > > > As I don't have audio where I am during the day, only Friday (when I > leave earlier in most cases) would work for me. > > Werner > > > On Tue, Jun 21, 2016 at 5:16 PM, <*cdi-dev-request(a)lists.jboss.org* > <cdi-dev-request(a)lists.jboss.org&gt;&gt; wrote: > Send cdi-dev mailing list submissions to > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt; > > To subscribe or unsubscribe via the World Wide Web, visit > *https://lists.jboss.org/mailman/listinfo/cdi-dev* > <https://lists.jboss.org/mailman/listinfo/cdi-dev> > or, via email, send a message with subject or body 'help' to > *cdi-dev-request(a)lists.jboss.org* > <cdi-dev-request(a)lists.jboss.org&gt; > > You can reach the person managing the list at > *cdi-dev-owner(a)lists.jboss.org* <cdi-dev-owner(a)lists.jboss.org&gt; > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. Re: CDI-30 hangout meeting (Antoine Sabot-Durand) > 2. Re: CDI-30 hangout meeting (John D. Ament) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 21 Jun 2016 15:13:54 +0000 > From: Antoine Sabot-Durand <*antoine(a)sabot-durand.net* > <antoine(a)sabot-durand.net&gt;&gt; > Subject: Re: [cdi-dev] CDI-30 hangout meeting > To: "John D. Ament" <*john.d.ament(a)gmail.com* <john.d.ament(a)gmail.com&gt;&gt;, > Martin Kouba > <*mkouba(a)redhat.com* <mkouba(a)redhat.com&gt;&gt;, Mark Struberg < > *struberg(a)yahoo.de* <struberg(a)yahoo.de&gt;&gt; > Cc: cdi-dev <*cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt;&gt; > Message-ID: > <CABu-YBQL7c_BUkBuZztSvnL4yrih4k5Vtvbz_-jf1K= > *z1n2gjQ(a)mail.gmail.com* <z1n2gjQ(a)mail.gmail.com&gt;&gt; > Content-Type: text/plain; charset="utf-8" > > So choices are Friday 24th 5:00 pm CET (same timeslot than our weekly > meeting) or Monday 27th 5:00pm CET. > I can do both but prefer Monday. > > What is your choice? > > Antoine > > Le mar. 21 juin 2016 ? 16:35, John D. Ament <*john.d.ament(a)gmail.com* > <john.d.ament(a)gmail.com&gt;&gt; a > ?crit : > > > I just went through the PR one more time. It seems like these are the > > areas of open discussion still: > > > > - The name of the class "ActiveContext" needs to be decided. I'm in > > agreement its a bad name, but switching to past tense doesn't help IMHO. > > - Disassociating the thread model and the context model. This is the > > first change that supports this initiative, so I'm not sure if there are > > any concerns with that change. > > - The fact that contexts have IDs. To me it makes sense, but it seems > > like this is not generally agreed (we need some unique identifier to > make > > sure we can bridge from existing) > > > > John > > > > > > On Tue, Jun 21, 2016 at 10:27 AM Martin Kouba <*mkouba(a)redhat.com* > <mkouba(a)redhat.com&gt;&gt; wrote: > > > >> I'm on PTO until Jun 29 :-( > >> > >> However, we've already discussed this with Antoine so I think my > >> presence is not required. > >> > >> Martin > >> > >> Dne 21.6.2016 v 16:23 John D. Ament napsal(a): > >> > Unfortunately, my schedule's turned south this week and Friday as of > now > >> > is the only day I have open. > >> > > >> > What about next week? Monday? > >> > > >> > John > >> > > >> > On Tue, Jun 21, 2016 at 4:42 AM Martin Kouba <*mkouba(a)redhat.com* > <mkouba(a)redhat.com&gt; > >> > <mailto:*mkouba@redhat.com* <mkouba(a)redhat.com&gt;&gt;&gt; wrote: > >> > > >> > 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] > >> > > >> > *http://docs.jboss.org/weld/reference/latest/en-US/html/contexts.html#_managing_the_built_in_contexts* > <http://docs.jboss.org/weld/reference/latest/en-US/html/contexts.html#_man... > >> > > >> > > >> > Dne 21.6.2016 v 09:22 Mark Struberg napsal(a): > >> > > 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* <antoine(a)sabot-durand.net&gt; <mailto: > *antoine(a)sabot-durand.net* <antoine(a)sabot-durand.net&gt;&gt;&gt;: > >> > >> > >> > >> 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* > <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* <cdi-dev(a)lists.jboss.org&gt; <mailto: > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt;&gt; > >> > >> *https://lists.jboss.org/mailman/listinfo/cdi-dev* > <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* > <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* <cdi-dev(a)lists.jboss.org&gt; <mailto: > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt;&gt; > >> > > *https://lists.jboss.org/mailman/listinfo/cdi-dev* > <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* > <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. > >> > > > >> > > >> > -- > >> > Martin Kouba > >> > Software Engineer > >> > Red Hat, Czech Republic > >> > _______________________________________________ > >> > cdi-dev mailing list > >> > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt; <mailto: > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt;&gt; > >> > *https://lists.jboss.org/mailman/listinfo/cdi-dev* > <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* > <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. > >> > > >> > >> -- > >> Martin Kouba > >> Software Engineer > >> Red Hat, Czech Republic > >> > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > *http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/c30cfd7d/attachment-0001.html* > <http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/c30cfd7d/at... > > ------------------------------ > > Message: 2 > Date: Tue, 21 Jun 2016 11:16:23 -0400 > From: "John D. Ament" <*john.d.ament(a)gmail.com* <john.d.ament(a)gmail.com&gt;&gt; > Subject: Re: [cdi-dev] CDI-30 hangout meeting > To: Antoine Sabot-Durand <*antoine(a)sabot-durand.net* > <antoine(a)sabot-durand.net&gt;&gt; > Cc: *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt; > Message-ID: > < > *CAOqetn_3uk-WxjhT438TFueB3_fYnXQfmw+NHpFrZ2BZ3ZJBXw(a)mail.gmail.com* > <CAOqetn_3uk-WxjhT438TFueB3_fYnXQfmw%2BNHpFrZ2BZ3ZJBXw(a)mail.gmail.com&gt;&gt; > Content-Type: text/plain; charset="utf-8" > > Monday is better for me but I can do both. > On Jun 21, 2016 11:14, "Antoine Sabot-Durand" <*antoine(a)sabot-durand.net* > <antoine(a)sabot-durand.net&gt;&gt; > wrote: > > > So choices are Friday 24th 5:00 pm CET (same timeslot than our weekly > > meeting) or Monday 27th 5:00pm CET. > > I can do both but prefer Monday. > > > > What is your choice? > > > > Antoine > > > > Le mar. 21 juin 2016 ? 16:35, John D. Ament <*john.d.ament(a)gmail.com* > <john.d.ament(a)gmail.com&gt;&gt; a > > ?crit : > > > >> I just went through the PR one more time. It seems like these are the > >> areas of open discussion still: > >> > >> - The name of the class "ActiveContext" needs to be decided. I'm in > >> agreement its a bad name, but switching to past tense doesn't help > IMHO. > >> - Disassociating the thread model and the context model. This is the > >> first change that supports this initiative, so I'm not sure if there > are > >> any concerns with that change. > >> - The fact that contexts have IDs. To me it makes sense, but it seems > >> like this is not generally agreed (we need some unique identifier to > make > >> sure we can bridge from existing) > >> > >> John > >> > >> > >> On Tue, Jun 21, 2016 at 10:27 AM Martin Kouba <*mkouba(a)redhat.com* > <mkouba(a)redhat.com&gt;&gt; wrote: > >> > >>> I'm on PTO until Jun 29 :-( > >>> > >>> However, we've already discussed this with Antoine so I think my > >>> presence is not required. > >>> > >>> Martin > >>> > >>> Dne 21.6.2016 v 16:23 John D. Ament napsal(a): > >>> > Unfortunately, my schedule's turned south this week and Friday as of > >>> now > >>> > is the only day I have open. > >>> > > >>> > What about next week? Monday? > >>> > > >>> > John > >>> > > >>> > On Tue, Jun 21, 2016 at 4:42 AM Martin Kouba <*mkouba(a)redhat.com* > <mkouba(a)redhat.com&gt; > >>> > <mailto:*mkouba@redhat.com* <mkouba(a)redhat.com&gt;&gt;&gt; wrote: > >>> > > >>> > 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] > >>> > > >>> > *http://docs.jboss.org/weld/reference/latest/en-US/html/contexts.html#_managing_the_built_in_contexts* > <http://docs.jboss.org/weld/reference/latest/en-US/html/contexts.html#_man... > >>> > > >>> > > >>> > Dne 21.6.2016 v 09:22 Mark Struberg napsal(a): > >>> > > 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* <antoine(a)sabot-durand.net&gt; <mailto: > *antoine(a)sabot-durand.net* <antoine(a)sabot-durand.net&gt;&gt;&gt;: > >>> > >> > >>> > >> 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* > <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* <cdi-dev(a)lists.jboss.org&gt; > <mailto:*cdi-dev@lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt;&gt; > >>> > >> *https://lists.jboss.org/mailman/listinfo/cdi-dev* > <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* > <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* <cdi-dev(a)lists.jboss.org&gt; <mailto: > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt;&gt; > >>> > > *https://lists.jboss.org/mailman/listinfo/cdi-dev* > <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* > <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. > >>> > > > >>> > > >>> > -- > >>> > Martin Kouba > >>> > Software Engineer > >>> > Red Hat, Czech Republic > >>> > _______________________________________________ > >>> > cdi-dev mailing list > >>> > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt; <mailto: > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt;&gt; > >>> > *https://lists.jboss.org/mailman/listinfo/cdi-dev* > <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* > <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. > >>> > > >>> > >>> -- > >>> Martin Kouba > >>> Software Engineer > >>> Red Hat, Czech Republic > >>> > >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > *http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/3e4c083b/attachment.html* > <http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/3e4c083b/at... > > ------------------------------ > > _______________________________________________ > cdi-dev mailing list > *cdi-dev(a)lists.jboss.org* <cdi-dev(a)lists.jboss.org&gt; > *https://lists.jboss.org/mailman/listinfo/cdi-dev* > <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* > <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. > > End of cdi-dev Digest, Vol 67, Issue 12 > *************************************** > _______________________________________________ > 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. > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU > > _______________________________________________ > 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.