From issues at jboss.org Wed Jun 1 07:22:00 2016 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 1 Jun 2016 07:22:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-611) Enhance 10.3.3. Multiple event qualifiers section In-Reply-To: References: Message-ID: Matej Novotny created CDI-611: --------------------------------- Summary: Enhance 10.3.3. Multiple event qualifiers section Key: CDI-611 URL: https://issues.jboss.org/browse/CDI-611 Project: CDI Specification Issues Issue Type: Clarification Components: Events Affects Versions: 2.0-EDR1 Reporter: Matej Novotny While the current spec is in fact correct, it is quite hard to decipher what it is actually trying to convey. Elsewhere in the spec, we talk about subsets of qualifiers while here we don't. There is a code sample and a sentence saying *"Then this observer method will only be notified if all the observed event qualifiers are specified when the event is fired:"* This can be interpreted as: * _"I must fire an event with exactly the same qualifiers as this observer has in order to notify it"_ (*wrong assumption* - it can have more qualifiers) * _"I must fire an event which will contain at least the same qualifiers as this observer has in order to notify it"_ (*correct* - yet not so obvious) I will try to come up with some improvement to make this clear. As it is, it always takes me several reading to soak it in. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 1 07:28:01 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Wed, 1 Jun 2016 07:28:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-611) Enhance 10.3.3. Multiple event qualifiers section In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246144#comment-13246144 ] John Ament commented on CDI-611: -------------------------------- The fact that event qualifiers and bean qualifiers don't work the same way is still an issue for a number of developers I've worked with. > Enhance 10.3.3. Multiple event qualifiers section > ------------------------------------------------- > > Key: CDI-611 > URL: https://issues.jboss.org/browse/CDI-611 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Events > Affects Versions: 2.0-EDR1 > Reporter: Matej Novotny > > While the current spec is in fact correct, it is quite hard to decipher what it is actually trying to convey. > Elsewhere in the spec, we talk about subsets of qualifiers while here we don't. There is a code sample and a sentence saying *"Then this observer method will only be notified if all the observed event qualifiers are specified when the event is fired:"* > This can be interpreted as: > * _"I must fire an event with exactly the same qualifiers as this observer has in order to notify it"_ (*wrong assumption* - it can have more qualifiers) > * _"I must fire an event which will contain at least the same qualifiers as this observer has in order to notify it"_ (*correct* - yet not so obvious) > I will try to come up with some improvement to make this clear. As it is, it always takes me several reading to soak it in. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 3 07:02:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Fri, 3 Jun 2016 07:02:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-612) ObserverMethodConfigurator.notifyWith() should probably accept a functional interface whose method throws java.lang.Exception In-Reply-To: References: Message-ID: Martin Kouba created CDI-612: -------------------------------- Summary: ObserverMethodConfigurator.notifyWith() should probably accept a functional interface whose method throws java.lang.Exception Key: CDI-612 URL: https://issues.jboss.org/browse/CDI-612 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 2.0-EDR1 Reporter: Martin Kouba The regular observer methods may also throw checked exceptions (wrapped and rethrown as an (unchecked) {{ObserverException}}). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 3 07:15:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Fri, 3 Jun 2016 07:15:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-612) ObserverMethodConfigurator.notifyWith() should probably accept a functional interface whose method throws java.lang.Exception In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Kouba updated CDI-612: ----------------------------- Fix Version/s: 2.0-EDR2 > ObserverMethodConfigurator.notifyWith() should probably accept a functional interface whose method throws java.lang.Exception > ----------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-612 > URL: https://issues.jboss.org/browse/CDI-612 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0-EDR1 > Reporter: Martin Kouba > Fix For: 2.0-EDR2 > > > The regular observer methods may also throw checked exceptions (wrapped and rethrown as an (unchecked) {{ObserverException}}). -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 3 12:51:00 2016 From: issues at jboss.org (Antoine Sabot-Durand (JIRA)) Date: Fri, 3 Jun 2016 12:51:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-613) Container should be able to receive information about the context in which it was bootstraped In-Reply-To: References: Message-ID: Antoine Sabot-Durand created CDI-613: ---------------------------------------- Summary: Container should be able to receive information about the context in which it was bootstraped Key: CDI-613 URL: https://issues.jboss.org/browse/CDI-613 Project: CDI Specification Issues Issue Type: Feature Request Components: Java EE integration Reporter: Antoine Sabot-Durand Today it's impossible to know what is the outside context of the CDI container (i.e what is the application or EE module it belongs to). This is problematic for other spec like JPA who needs to retrieve their information (persistence units) from a portable extension. This would help solving issues like WFLY-2387 in a portable way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 3 12:52:00 2016 From: issues at jboss.org (Antoine Sabot-Durand (JIRA)) Date: Fri, 3 Jun 2016 12:52:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-613) Container should be able to receive information about the context in which it was bootstraped In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antoine Sabot-Durand updated CDI-613: ------------------------------------- Fix Version/s: 2.0 (proposed) > Container should be able to receive information about the context in which it was bootstraped > --------------------------------------------------------------------------------------------- > > Key: CDI-613 > URL: https://issues.jboss.org/browse/CDI-613 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Reporter: Antoine Sabot-Durand > Fix For: 2.0 (proposed) > > > Today it's impossible to know what is the outside context of the CDI container (i.e what is the application or EE module it belongs to). > This is problematic for other spec like JPA who needs to retrieve their information (persistence units) from a portable extension. > This would help solving issues like WFLY-2387 in a portable way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From struberg at yahoo.de Mon Jun 6 00:40:54 2016 From: struberg at yahoo.de (Mark Struberg) Date: Mon, 6 Jun 2016 04:40:54 +0000 (UTC) Subject: [cdi-dev] 'implicit bean' definition, section 2.5.1 References: <1276730719.1621128.1465188054125.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <1276730719.1621128.1465188054125.JavaMail.yahoo@mail.yahoo.com> "A bean class with a bean defining annotation is said to be an implicit bean." That sounds pretty weird to me. I would have expected it exactly the other way around. A bean with a @SessionScoped annotation is rather an explicit bean to me. Any reason for this section? LieGrue, strub From manovotn at redhat.com Mon Jun 6 02:25:24 2016 From: manovotn at redhat.com (Matej Novotny) Date: Mon, 6 Jun 2016 02:25:24 -0400 (EDT) Subject: [cdi-dev] 'implicit bean' definition, section 2.5.1 In-Reply-To: <1276730719.1621128.1465188054125.JavaMail.yahoo@mail.yahoo.com> References: <1276730719.1621128.1465188054125.JavaMail.yahoo.ref@mail.yahoo.com> <1276730719.1621128.1465188054125.JavaMail.yahoo@mail.yahoo.com> Message-ID: <2092132098.57257232.1465194324722.JavaMail.zimbra@redhat.com> Hi Mark I think there is a reason for that. Look at section "12.1. Bean archives" -> "An implicit bean archive is any other archive which contains one or more bean classes with a bean defining annotation as defined in Bean defining annotations." (E.g. which contains one or more implicit beans) Basically, "implicit bean" creates a basis for definition on "implicit bean archive" (and, as opposed to that, "explicit bean archive"). I think you want to use explicit/implicit to define archives (based on presence/absence of beans.xml). And from that you derive that implicit archive contains implicit beans. Matej ----- Original Message ----- > From: "Mark Struberg" > To: "Cdi-dev" > Sent: Monday, June 6, 2016 6:40:54 AM > Subject: [cdi-dev] 'implicit bean' definition, section 2.5.1 > > "A bean class with a bean defining annotation is said to be an implicit > bean." > > That sounds pretty weird to me. I would have expected it exactly the other > way around. > A bean with a @SessionScoped annotation is rather an explicit bean to me. > > Any reason for this section? > > 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. > From issues at jboss.org Mon Jun 6 05:44:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Mon, 6 Jun 2016 05:44:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-613) Container should be able to receive information about the context in which it was bootstraped In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248134#comment-13248134 ] Martin Kouba commented on CDI-613: ---------------------------------- I believe it is a more general problem (not only Java EE). A portable extension is instantiated by the CDI container and as such has no "reference" to any related technology/framework resources during bootstrap (i.e. during container lifecycle event delivery). So I think a kind of _"bootstrap configuration/metadata"_ is missing. The truth is this would probably require a standardized Bootstrap API. And this would be tricky, especially in the context of Java EE. > Container should be able to receive information about the context in which it was bootstraped > --------------------------------------------------------------------------------------------- > > Key: CDI-613 > URL: https://issues.jboss.org/browse/CDI-613 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Reporter: Antoine Sabot-Durand > Fix For: 2.0 (proposed) > > > Today it's impossible to know what is the outside context of the CDI container (i.e what is the application or EE module it belongs to). > This is problematic for other spec like JPA who needs to retrieve their information (persistence units) from a portable extension. > This would help solving issues like WFLY-2387 in a portable way. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 08:23:00 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Mon, 6 Jun 2016 08:23:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248238#comment-13248238 ] Mark Struberg commented on CDI-420: ----------------------------------- I thought about this now for quite a few weeks. I think we should still address this within the spec. It would be a shame if we would have to add an Extension for this. It should really be part of core CDI. There are 2 options left in the game: 1.) {code} .. {code} 2.) {code} false {code} > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 6 09:01:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Mon, 6 Jun 2016 09:01:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248283#comment-13248283 ] Martin Kouba commented on CDI-420: ---------------------------------- Hm, what about making it more generic? E.g. something like introducing "exclude filters" for Bean discovery: {code:xml} {code} > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From struberg at yahoo.de Tue Jun 7 00:53:27 2016 From: struberg at yahoo.de (Mark Struberg) Date: Tue, 7 Jun 2016 06:53:27 +0200 Subject: [cdi-dev] 'implicit bean' definition, section 2.5.1 In-Reply-To: <2092132098.57257232.1465194324722.JavaMail.zimbra@redhat.com> References: <1276730719.1621128.1465188054125.JavaMail.yahoo.ref@mail.yahoo.com> <1276730719.1621128.1465188054125.JavaMail.yahoo@mail.yahoo.com> <2092132098.57257232.1465194324722.JavaMail.zimbra@redhat.com> Message-ID: Oki, txs. I can follow the explanation - but the result still sounds awesome wrong ;) The _archive_ is implicit, but the beans inside it are imo not. A class with @RequestScoped is pretty much as explicit about it?s ?bean-ness? as it can get ;) Without your explanation I would have guessed that an ?Implicit Bean? is everything which gets a @Dependent scope by rule. E.g. Interceptors, Decorators and classes which become auto-dependent. I?d rather have argued that ?if a java archive contains an explicit Bean then the archive becomes an Implicit Bean Archive? But not sure we can change this now. LieGrue, strub > Am 06.06.2016 um 08:25 schrieb Matej Novotny : > > Hi Mark > > I think there is a reason for that. > Look at section "12.1. Bean archives" -> "An implicit bean archive is any other archive which > contains one or more bean classes with a bean defining annotation as defined in Bean defining annotations." (E.g. which contains one or more implicit beans) > > Basically, "implicit bean" creates a basis for definition on "implicit bean archive" (and, as opposed to that, "explicit bean archive"). > I think you want to use explicit/implicit to define archives (based on presence/absence of beans.xml). And from that you derive that implicit archive contains implicit beans. > > > Matej > > ----- Original Message ----- >> From: "Mark Struberg" >> To: "Cdi-dev" >> Sent: Monday, June 6, 2016 6:40:54 AM >> Subject: [cdi-dev] 'implicit bean' definition, section 2.5.1 >> >> "A bean class with a bean defining annotation is said to be an implicit >> bean." >> >> That sounds pretty weird to me. I would have expected it exactly the other >> way around. >> A bean with a @SessionScoped annotation is rather an explicit bean to me. >> >> Any reason for this section? >> >> 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. >> From issues at jboss.org Tue Jun 7 04:52:00 2016 From: issues at jboss.org (Tomas Remes (JIRA)) Date: Tue, 7 Jun 2016 04:52:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-614) Review all read methods at configurators In-Reply-To: References: Message-ID: Tomas Remes created CDI-614: ------------------------------- Summary: Review all read methods at configurators Key: CDI-614 URL: https://issues.jboss.org/browse/CDI-614 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 2.0-EDR2 Reporter: Tomas Remes Currently there are several read methods used to initialize given configurator. These methods are at: * {{BeanConfigurator}} * {{InjectionPointConfigurator}} * {{ObserverMethodConfigurator}} I think we should review all of them. I don't understand to usage or let say additional value of the following ones: * {{ObserverMethodConfigurator#read(javax.enterprise.inject.spi.ObserverMethod)}} This allows you to add new observer method based on exsiting one. Although when you want to define some observed type (of this new method) you need to specify subtype of the original type or you will end up with ClassCastException. Then there are those at {{InjectionPointConfigurator}} which appears to me completely useless: * {{InjectionPointConfigurator#read(java.lang.reflect.Field)}} * {{InjectionPointConfigurator#read(java.lang.reflect.Parameter)}} * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.AnnotatedField)}} * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.AnnotatedParameter)}} * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.InjectionPoint)}} AFAIK the {{InjectionPointConfigurator}} is available only during {{ProcessInjectionPoint}} lifecycle event. My question is why should I use any of these during this lifecycle event since I can easily call {{event.configureInjectionPoint()}}? Do we want to allow to configure different injection point in non corresponding {{ProcessInjectionPoint}} lifecycle event? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From tremes at redhat.com Tue Jun 7 04:59:35 2016 From: tremes at redhat.com (Tomas Remes) Date: Tue, 7 Jun 2016 04:59:35 -0400 (EDT) Subject: [cdi-dev] configurators and read methods In-Reply-To: <2041542539.13062779.1465289620071.JavaMail.zimbra@redhat.com> Message-ID: <720146631.13066462.1465289975703.JavaMail.zimbra@redhat.com> Hi EG! Recently I created https://issues.jboss.org/browse/CDI-614 and would like to ask you to review and share your opinion on this. I wanted to finish TCK tests for InjectionPointConfigurator but I realized that I don't understand the purpose of its read methods at all.:-) There are few other read methods on different configurators and I think we should think about them whether they are really useful or not. I personally don't like this approach as I stated in comment in related CDI-609. Thank's a lot -- Tomas Remes From issues at jboss.org Tue Jun 7 05:00:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Tue, 7 Jun 2016 05:00:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-614) Review all read methods at configurators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248773#comment-13248773 ] Martin Kouba commented on CDI-614: ---------------------------------- bq. AFAIK the InjectionPointConfigurator is available only during ProcessInjectionPoint lifecycle event. Yes, it is. We've discussed the possibilities to use the {{InjectionPointConfigurator}} within {{BeanConfigurator}}, but in fact, all those injection point-related methods on {{BeanConfigurator}} are disputable as well (note that {{Bean.getInjectionPoints()}} is only used for validation, not for injection). > Review all read methods at configurators > ---------------------------------------- > > Key: CDI-614 > URL: https://issues.jboss.org/browse/CDI-614 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0-EDR2 > Reporter: Tomas Remes > > Currently there are several read methods used to initialize given configurator. These methods are at: > * {{BeanConfigurator}} > * {{InjectionPointConfigurator}} > * {{ObserverMethodConfigurator}} > I think we should review all of them. I don't understand to usage or let say additional value of the following ones: > * {{ObserverMethodConfigurator#read(javax.enterprise.inject.spi.ObserverMethod)}} > This allows you to add new observer method based on exsiting one. Although when you want to define some observed type (of this new method) you need to specify subtype of the original type or you will end up with ClassCastException. > Then there are those at {{InjectionPointConfigurator}} which appears to me completely useless: > * {{InjectionPointConfigurator#read(java.lang.reflect.Field)}} > * {{InjectionPointConfigurator#read(java.lang.reflect.Parameter)}} > * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.AnnotatedField)}} > * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.AnnotatedParameter)}} > * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.InjectionPoint)}} > AFAIK the {{InjectionPointConfigurator}} is available only during {{ProcessInjectionPoint}} lifecycle event. My question is why should I use any of these during this lifecycle event since I can easily call {{event.configureInjectionPoint()}}? Do we want to allow to configure different injection point in non corresponding {{ProcessInjectionPoint}} lifecycle event? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 07:32:00 2016 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Tue, 7 Jun 2016 07:32:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-614) Review all read methods at configurators In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248870#comment-13248870 ] Matej Novotny commented on CDI-614: ----------------------------------- bq. all those injection point-related methods on {{BeanConfigurator}} are disputable as well +1 for that. I mentioned it somewhere already; you can set an injection point with {{BeanConfigurator}} but you cannot achieve the injection itself. And to share my opinion on read methods: As for {{read}} methods on {{BeanConfigurator}}, I would say those are fine. Are won't bounce into ClassCastException there and it might prove handy to read a bean you already have and with that basis you build a new one. Furthermore, amongst {{ObserverMethodConfigurator#read*}} I really dislike {{read(javax.enterprise.inject.spi.ObserverMethod)}}. +1 for removing this. Others can still be used IMHO as they are not susceptible to ClassCastExceptions and easy to use. Last but not least {{InjectionPointConfigurator#read}}. Those seems pretty useless. I understand read methods when you need to create something from the scratch, but when you are simply adjusting it, it doesn't make much sense. > Review all read methods at configurators > ---------------------------------------- > > Key: CDI-614 > URL: https://issues.jboss.org/browse/CDI-614 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0-EDR2 > Reporter: Tomas Remes > > Currently there are several read methods used to initialize given configurator. These methods are at: > * {{BeanConfigurator}} > * {{InjectionPointConfigurator}} > * {{ObserverMethodConfigurator}} > I think we should review all of them. I don't understand to usage or let say additional value of the following ones: > * {{ObserverMethodConfigurator#read(javax.enterprise.inject.spi.ObserverMethod)}} > This allows you to add new observer method based on exsiting one. Although when you want to define some observed type (of this new method) you need to specify subtype of the original type or you will end up with ClassCastException. > Then there are those at {{InjectionPointConfigurator}} which appears to me completely useless: > * {{InjectionPointConfigurator#read(java.lang.reflect.Field)}} > * {{InjectionPointConfigurator#read(java.lang.reflect.Parameter)}} > * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.AnnotatedField)}} > * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.AnnotatedParameter)}} > * {{InjectionPointConfigurator#read(javax.enterprise.inject.spi.InjectionPoint)}} > AFAIK the {{InjectionPointConfigurator}} is available only during {{ProcessInjectionPoint}} lifecycle event. My question is why should I use any of these during this lifecycle event since I can easily call {{event.configureInjectionPoint()}}? Do we want to allow to configure different injection point in non corresponding {{ProcessInjectionPoint}} lifecycle event? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 08:23:00 2016 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Tue, 7 Jun 2016 08:23:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248909#comment-13248909 ] Matej Novotny commented on CDI-420: ----------------------------------- While I still feel that addressing this with an Extension would be sufficient, I have to say that Martin's solution is pretty elegant. I doesn't add any new complexity to bean discovery modes as you keep using current ones and it works on a familiar exclusion basis. Plus, as was pointed out to me, it can be done on a per-archive basis compared to extension which would be global. To sum it up - +1 for this solution. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 08:25:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Tue, 7 Jun 2016 08:25:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248283#comment-13248283 ] Martin Kouba edited comment on CDI-420 at 6/7/16 8:24 AM: ---------------------------------------------------------- Hm, what about making it more generic? E.g. something like introducing "exclude filters" for Bean discovery: {code:xml} {code} was (Author: mkouba): Hm, what about making it more generic? E.g. something like introducing "exclude filters" for Bean discovery: {code:xml} {code} > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 08:27:00 2016 From: issues at jboss.org (Antoine Sabot-Durand (JIRA)) Date: Tue, 7 Jun 2016 08:27:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248912#comment-13248912 ] Antoine Sabot-Durand commented on CDI-420: ------------------------------------------ +1 for Martin approach. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 08:35:00 2016 From: issues at jboss.org (Samba Siva Rao Kolusu (JIRA)) Date: Tue, 7 Jun 2016 08:35:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-615) provide API to register new beans to the context after deployment (at runtime) In-Reply-To: References: Message-ID: Samba Siva Rao Kolusu created CDI-615: ----------------------------------------- Summary: provide API to register new beans to the context after deployment (at runtime) Key: CDI-615 URL: https://issues.jboss.org/browse/CDI-615 Project: CDI Specification Issues Issue Type: Feature Request Components: Beans Affects Versions: 1.2.Final Environment: N/A Reporter: Samba Siva Rao Kolusu CDI provides API to listen/observe for various stages of bean discovery and deployment, during which we can add additional types to be registered as managed CDI beans/interceptors/etc. however, there is no way to do the same (i.e.) register new types as CDI managed beans/interceptors/etc once the application is deployed (i.e. during runtime). it would be very useful if the spec is enhanced to also provide a runtime API to register new types as Beans or Interceptors. this is what we do currently: {code:java} public void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event, BeanManager beanManager) { this.bm=beanManager; Set> klasses=get classes from from some non-jee-classpath AnnotatedType annotatedType; for(Class klass : klasses ) { annotatedType = bm.createAnnotatedType(klass); _*event.addAnnotatedType(annotatedType,klass.getName());*_ } } {code} something like the following will be of great use: {code:java} @Inject BeanManager bm; AnnotatedType annotatedType = bm.createAnnotatedType(klass); _*bm.addAnnotatedType(annotatedType,klass.getName());*_ {code} this simple API will help discover beans after deployment or from non-jee classpaths. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 08:35:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Tue, 7 Jun 2016 08:35:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248283#comment-13248283 ] Martin Kouba edited comment on CDI-420 at 6/7/16 8:34 AM: ---------------------------------------------------------- Hm, what about making it more generic? E.g. something like introducing "exclude filters" for Bean discovery: {code:xml} {code} was (Author: mkouba): Hm, what about making it more generic? E.g. something like introducing "exclude filters" for Bean discovery: {code:xml} {code} > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 08:37:00 2016 From: issues at jboss.org (Samba Siva Rao Kolusu (JIRA)) Date: Tue, 7 Jun 2016 08:37:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-615) provide API to register new beans to the context after deployment (at runtime) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samba Siva Rao Kolusu updated CDI-615: -------------------------------------- Description: # CDI provides API to listen/observe for various stages of bean discovery and deployment, during which we can add additional types to be registered as managed CDI beans/interceptors/etc. however, there is no way to do the same (i.e.) register new types as CDI managed beans/interceptors/etc once the application is deployed (i.e. during runtime). it would be very useful if the spec is enhanced to also provide a runtime API to register new types as Beans or Interceptors. this is what we do currently: {code:java} public void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event, BeanManager beanManager) { this.bm=beanManager; Set> klasses=get classes from from some non-jee-classpath AnnotatedType annotatedType; for(Class klass : klasses ) { annotatedType = bm.createAnnotatedType(klass); _*event.addAnnotatedType(annotatedType,klass.getName());*_ } } {code} something like the following will be of great use: {code:java} @Inject BeanManager bm; AnnotatedType annotatedType = bm.createAnnotatedType(klass); _*bm.addAnnotatedType(annotatedType,klass.getName());*_ {code} this simple API will help discover beans after deployment or from non-jee classpaths. was: CDI provides API to listen/observe for various stages of bean discovery and deployment, during which we can add additional types to be registered as managed CDI beans/interceptors/etc. however, there is no way to do the same (i.e.) register new types as CDI managed beans/interceptors/etc once the application is deployed (i.e. during runtime). it would be very useful if the spec is enhanced to also provide a runtime API to register new types as Beans or Interceptors. this is what we do currently: {code:java} public void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event, BeanManager beanManager) { this.bm=beanManager; Set> klasses=get classes from from some non-jee-classpath AnnotatedType annotatedType; for(Class klass : klasses ) { annotatedType = bm.createAnnotatedType(klass); _*event.addAnnotatedType(annotatedType,klass.getName());*_ } } {code} something like the following will be of great use: {code:java} @Inject BeanManager bm; AnnotatedType annotatedType = bm.createAnnotatedType(klass); _*bm.addAnnotatedType(annotatedType,klass.getName());*_ {code} this simple API will help discover beans after deployment or from non-jee classpaths. > provide API to register new beans to the context after deployment (at runtime) > ------------------------------------------------------------------------------ > > Key: CDI-615 > URL: https://issues.jboss.org/browse/CDI-615 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.2.Final > Environment: N/A > Reporter: Samba Siva Rao Kolusu > > # CDI provides API to listen/observe for various stages of bean discovery and deployment, during which we can add additional types to be registered as managed CDI beans/interceptors/etc. however, there is no way to do the same (i.e.) register new types as CDI managed beans/interceptors/etc once the application is deployed (i.e. during runtime). > it would be very useful if the spec is enhanced to also provide a runtime API to register new types as Beans or Interceptors. > this is what we do currently: > {code:java} > public void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event, BeanManager beanManager) { > this.bm=beanManager; > Set> klasses=get classes from from some non-jee-classpath > AnnotatedType annotatedType; > for(Class klass : klasses ) { > annotatedType = bm.createAnnotatedType(klass); > _*event.addAnnotatedType(annotatedType,klass.getName());*_ > } > } > {code} > something like the following will be of great use: > {code:java} > @Inject BeanManager bm; > AnnotatedType annotatedType = bm.createAnnotatedType(klass); > _*bm.addAnnotatedType(annotatedType,klass.getName());*_ > {code} > this simple API will help discover beans after deployment or from non-jee classpaths. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 08:38:00 2016 From: issues at jboss.org (Samba Siva Rao Kolusu (JIRA)) Date: Tue, 7 Jun 2016 08:38:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-615) provide API to register new beans to the context after deployment (at runtime) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samba Siva Rao Kolusu updated CDI-615: -------------------------------------- Description: # CDI provides API to listen/observe for various stages of bean discovery and deployment, during which we can add additional types to be registered as managed CDI beans/interceptors/etc. however, there is no way to do the same (i.e.) register new types as CDI managed beans/interceptors/etc once the application is deployed (i.e. during runtime). it would be very useful if the spec is enhanced to also provide a runtime API to register new types as Beans or Interceptors. this is what we do currently: {code:java} public void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event, BeanManager beanManager) { this.bm=beanManager; Set> klasses=get classes from from some non-jee-classpath AnnotatedType annotatedType; for(Class klass : klasses ) { annotatedType = bm.createAnnotatedType(klass); event.addAnnotatedType(annotatedType,klass.getName()); } } {code} something like the following will be of great use: {code:java} @Inject BeanManager bm; AnnotatedType annotatedType = bm.createAnnotatedType(klass); bm.addAnnotatedType(annotatedType,klass.getName()); {code} this simple API will help discover beans after deployment or from non-jee classpaths. was: # CDI provides API to listen/observe for various stages of bean discovery and deployment, during which we can add additional types to be registered as managed CDI beans/interceptors/etc. however, there is no way to do the same (i.e.) register new types as CDI managed beans/interceptors/etc once the application is deployed (i.e. during runtime). it would be very useful if the spec is enhanced to also provide a runtime API to register new types as Beans or Interceptors. this is what we do currently: {code:java} public void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event, BeanManager beanManager) { this.bm=beanManager; Set> klasses=get classes from from some non-jee-classpath AnnotatedType annotatedType; for(Class klass : klasses ) { annotatedType = bm.createAnnotatedType(klass); _*event.addAnnotatedType(annotatedType,klass.getName());*_ } } {code} something like the following will be of great use: {code:java} @Inject BeanManager bm; AnnotatedType annotatedType = bm.createAnnotatedType(klass); _*bm.addAnnotatedType(annotatedType,klass.getName());*_ {code} this simple API will help discover beans after deployment or from non-jee classpaths. > provide API to register new beans to the context after deployment (at runtime) > ------------------------------------------------------------------------------ > > Key: CDI-615 > URL: https://issues.jboss.org/browse/CDI-615 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.2.Final > Environment: N/A > Reporter: Samba Siva Rao Kolusu > > # CDI provides API to listen/observe for various stages of bean discovery and deployment, during which we can add additional types to be registered as managed CDI beans/interceptors/etc. however, there is no way to do the same (i.e.) register new types as CDI managed beans/interceptors/etc once the application is deployed (i.e. during runtime). > it would be very useful if the spec is enhanced to also provide a runtime API to register new types as Beans or Interceptors. > this is what we do currently: > {code:java} > public void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event, BeanManager beanManager) { > this.bm=beanManager; > Set> klasses=get classes from from some non-jee-classpath > AnnotatedType annotatedType; > for(Class klass : klasses ) { > annotatedType = bm.createAnnotatedType(klass); > event.addAnnotatedType(annotatedType,klass.getName()); > } > } > {code} > something like the following will be of great use: > {code:java} > @Inject BeanManager bm; > AnnotatedType annotatedType = bm.createAnnotatedType(klass); > bm.addAnnotatedType(annotatedType,klass.getName()); > {code} > this simple API will help discover beans after deployment or from non-jee classpaths. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 08:44:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Tue, 7 Jun 2016 08:44:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-615) provide API to register new beans to the context after deployment (at runtime) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Kouba resolved CDI-615. ------------------------------ Resolution: Duplicate Issue > provide API to register new beans to the context after deployment (at runtime) > ------------------------------------------------------------------------------ > > Key: CDI-615 > URL: https://issues.jboss.org/browse/CDI-615 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.2.Final > Environment: N/A > Reporter: Samba Siva Rao Kolusu > > # CDI provides API to listen/observe for various stages of bean discovery and deployment, during which we can add additional types to be registered as managed CDI beans/interceptors/etc. however, there is no way to do the same (i.e.) register new types as CDI managed beans/interceptors/etc once the application is deployed (i.e. during runtime). > it would be very useful if the spec is enhanced to also provide a runtime API to register new types as Beans or Interceptors. > this is what we do currently: > {code:java} > public void beforeBeanDiscovery(@Observes BeforeBeanDiscovery event, BeanManager beanManager) { > this.bm=beanManager; > Set> klasses=get classes from from some non-jee-classpath > AnnotatedType annotatedType; > for(Class klass : klasses ) { > annotatedType = bm.createAnnotatedType(klass); > event.addAnnotatedType(annotatedType,klass.getName()); > } > } > {code} > something like the following will be of great use: > {code:java} > @Inject BeanManager bm; > AnnotatedType annotatedType = bm.createAnnotatedType(klass); > bm.addAnnotatedType(annotatedType,klass.getName()); > {code} > this simple API will help discover beans after deployment or from non-jee classpaths. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 09:35:01 2016 From: issues at jboss.org (Emily Jiang (JIRA)) Date: Tue, 7 Jun 2016 09:35:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248972#comment-13248972 ] Emily Jiang commented on CDI-420: --------------------------------- I am a bit confused. I thought this discussion is to include some classes that are not beans in the implicit bean archives. In Martin's suggestion, it is to exclude classes. Do you mean "include" or I might have missed something? > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Tue Jun 7 09:43:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Tue, 7 Jun 2016 09:43:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248977#comment-13248977 ] Martin Kouba commented on CDI-420: ---------------------------------- [~emilyj] Not really, the point is to fire {{ProcessAnnotatedType}} even for classes which are not annotated with a bean defining annotation but do not register these classes as beans. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From antoine at sabot-durand.net Tue Jun 7 10:17:05 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Tue, 07 Jun 2016 14:17:05 +0000 Subject: [cdi-dev] Canceling today's meeting Message-ID: Hi all, Unfortunately I have a kid emergency and won't be available for the meeting. Antoine -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160607/2531963a/attachment.html From issues at jboss.org Tue Jun 7 17:44:01 2016 From: issues at jboss.org (Emily Jiang (JIRA)) Date: Tue, 7 Jun 2016 17:44:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249265#comment-13249265 ] Emily Jiang commented on CDI-420: --------------------------------- Martin, can you elaborate a bit more on how to achieve the requirement of processing all classes with the exclude filter? > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 8 01:21:00 2016 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 8 Jun 2016 01:21:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249325#comment-13249325 ] Matej Novotny commented on CDI-420: ----------------------------------- [~emilyj] Use bean discovery mode {{all}} and add the exclude filter. That means it will pick up even classes without bean defining annotation and fire PAT for them, yet if they are in the exclusion filter it won't pick them up as Beans. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 8 01:21:00 2016 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Wed, 8 Jun 2016 01:21:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249325#comment-13249325 ] Matej Novotny edited comment on CDI-420 at 6/8/16 1:20 AM: ----------------------------------------------------------- [~emilyj] Use bean discovery mode {{all}} and add the exclusion filter. That means it will pick up even classes without bean defining annotation and fire PAT for them, yet if they are in the exclusion filter it won't pick them up as Beans. was (Author: manovotn): [~emilyj] Use bean discovery mode {{all}} and add the exclude filter. That means it will pick up even classes without bean defining annotation and fire PAT for them, yet if they are in the exclusion filter it won't pick them up as Beans. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 8 01:43:00 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Wed, 8 Jun 2016 01:43:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249330#comment-13249330 ] Mark Struberg commented on CDI-420: ----------------------------------- I fear it's confusing for the user. Please remember that the whole ticket is mostly for fixing a behaviour which is imo broken since the very early days: to prevent automatically pick up all classes as @Dependent scoped beans, even if they have no single CDI annotation at all. Those are in 99.9999% cases just pure waste in our memory. Otoh we cannot enable this for all classes as there might be some jars which depend on it. Thus we need to activate this per classpath entry. There was a first attempt to fix this behaviour with the bean-discovery-mode="anotated". And it didn't work out because of the aforementioned problems. I thought about Martins proposal for two days now. It is certainly interesting but I don't yet see any benefit in having a second configurable exclude mechanism which exceeds this basic rules. Are there any other use cases you have in mind? Because if the above reason is the only one then I find it overreaching. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 8 02:01:01 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Wed, 8 Jun 2016 02:01:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249332#comment-13249332 ] Mark Struberg commented on CDI-420: ----------------------------------- [~manovotn] sorry, we overlapped when editing. Yes, "all" (or the implicit CDI-1.0 mode) was really intentional. When using "annotated" you don't even get that far. Interfaces and non-annotated classes will not even make it to ProcessAnnotatedType. Thus there is nothing to exclude - because they don't even get processed ;) > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 8 03:10:00 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Wed, 8 Jun 2016 03:10:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249344#comment-13249344 ] Martin Kouba commented on CDI-420: ---------------------------------- [~struberg] So the only argument is "it's confusing for users"? Frankly speaking, any solution will be confusing for users. I proposed a new solution because I don't think it's a good idea to introduce a new bean discovery mode which is almost identical to {{annotated}} (also the name {{scoped}} is definitely not accurate). Having a special tag is not elegant either. So I've tried to propose an extensible solution which is more like a new feature. I did not have any other use cases in mind, although the {{}} might be also useful. I agree that it's more verbose though. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 8 17:52:00 2016 From: issues at jboss.org (Emily Jiang (JIRA)) Date: Wed, 8 Jun 2016 17:52:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249954#comment-13249954 ] Emily Jiang commented on CDI-420: --------------------------------- Thank you Matej for the explanation! Since Martin's snippet does not mention bean-discovery-mode, I thought it was the default one, "annotated". Hence the confusion. If the proposal is to add exclusion in the mode of bean-discovery-mode="all", it seems to introduce a half veto, opting in for Type Discovery but not Bean Discovery. I think this should work and involves less change. I think if we directly expand the section 12.4.2. Exclude filters, we might be able to explain well. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 9 02:02:01 2016 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 9 Jun 2016 02:02:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250019#comment-13250019 ] Matej Novotny commented on CDI-420: ----------------------------------- [~emilyj] to be precise, Martin's snippet could be used in both, "all" and "annotated" modes. To achieve the behaviour described in this issue, you obviously want to use it with "all". But sometimes it might be useful to use it with "annotated" - that way it would allow you to "veto" beans which actually have bean defining annotation. So all in all, this solution also offer some covers other possible use cases. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 9 02:03:00 2016 From: issues at jboss.org (Matej Novotny (JIRA)) Date: Thu, 9 Jun 2016 02:03:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250019#comment-13250019 ] Matej Novotny edited comment on CDI-420 at 6/9/16 2:02 AM: ----------------------------------------------------------- [~emilyj] to be precise, Martin's snippet could be used in both, "all" and "annotated" modes. To achieve the behaviour described in this issue, you obviously want to use it with "all". But sometimes it might be useful to use it with "annotated" - that way it would allow you to "veto" beans which actually have bean defining annotation. So all in all, this solution also offer some covers other possible use cases. bq. I think this should work and involves less change. I think if we directly expand the section 12.4.2. Exclude filters, we might be able to explain well. Agreed, that would be a great place to explain this. was (Author: manovotn): [~emilyj] to be precise, Martin's snippet could be used in both, "all" and "annotated" modes. To achieve the behaviour described in this issue, you obviously want to use it with "all". But sometimes it might be useful to use it with "annotated" - that way it would allow you to "veto" beans which actually have bean defining annotation. So all in all, this solution also offer some covers other possible use cases. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 9 05:25:00 2016 From: issues at jboss.org (Emily Jiang (JIRA)) Date: Thu, 9 Jun 2016 05:25:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250097#comment-13250097 ] Emily Jiang commented on CDI-420: --------------------------------- I had a further thought on this: We could introduce 'include'. {code:java} {code} This will cause the classes to be scanned and opted in for type discovery. It is similar to Martin's approach. Is this easier to be understood? just my 2cents. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Thu Jun 9 05:48:01 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Thu, 9 Jun 2016 05:48:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250108#comment-13250108 ] Martin Kouba commented on CDI-420: ---------------------------------- [~emilyj] This will not help. Right now, a class is discovered if it has a bean defining annotation *&&* is not excluded (for an implicit bean archive). In other words, the container first tests whether a class has a bean defining annotation and if it has, then container applies filters. We would have to modify the wording in an incompatible way. Also we would have to specify what happens if include/exclude are matched at the same time. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 02:33:00 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Fri, 10 Jun 2016 02:33:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250650#comment-13250650 ] Mark Struberg commented on CDI-420: ----------------------------------- [~mkouba] My main argument is that nobody was able to show any benefit over the simple form yet. I cannot _yet_ see any use case beyond "". And "" is again so specific that it is not reusable for other cases. So it basically can be reduced to {code} {code} Bring me good use cases where your additional sugar is useful and I'm sold ;) > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 02:34:00 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Fri, 10 Jun 2016 02:34:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250650#comment-13250650 ] Mark Struberg edited comment on CDI-420 at 6/10/16 2:33 AM: ------------------------------------------------------------ [~mkouba] My main argument is that nobody was able to show any benefit over the simple form yet. I cannot _yet_ see any use case beyond "". And "" is again so specific that it is not reusable for other cases. So it basically can be reduced to {code} {code} Bring me good use cases where your additional sugar is useful and I'm sold ;) was (Author: struberg): [~mkouba] My main argument is that nobody was able to show any benefit over the simple form yet. I cannot _yet_ see any use case beyond "". And "" is again so specific that it is not reusable for other cases. So it basically can be reduced to {code} {code} Bring me good use cases where your additional sugar is useful and I'm sold ;) > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 02:34:00 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Fri, 10 Jun 2016 02:34:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250650#comment-13250650 ] Mark Struberg edited comment on CDI-420 at 6/10/16 2:33 AM: ------------------------------------------------------------ [~mkouba] My main argument is that nobody was able to show any benefit over the simple form yet. I cannot _yet_ see any use case beyond "". And "" is again so specific that it is not reusable for other cases. So it basically can be reduced to {code} {code} Bring me good use cases where your additional sugar is useful and I'm sold ;) was (Author: struberg): [~mkouba] My main argument is that nobody was able to show any benefit over the simple form yet. I cannot _yet_ see any use case beyond "". And "" is again so specific that it is not reusable for other cases. So it basically can be reduced to {code} {code} Bring me good use cases where your additional sugar is useful and I'm sold ;) > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 05:14:00 2016 From: issues at jboss.org (Emily Jiang (JIRA)) Date: Fri, 10 Jun 2016 05:14:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: Emily Jiang created CDI-616: ------------------------------- Summary: Injection point declared as transient is not useful Key: CDI-616 URL: https://issues.jboss.org/browse/CDI-616 Project: CDI Specification Issues Issue Type: Clarification Components: Concepts Affects Versions: 1.2.Final Environment: n/a Reporter: Emily Jiang Priority: Minor An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? The isTransient() method returns true if the injection point is a transient field, and false otherwise. If the injection point represents a dynamically obtained instance then the isTransient() method returns true if the Instance injection point is a transient field, and false otherwise. => The isTransient() method returns true if the injection point is a transient field, and false otherwise. If the injection point represents a dynamically obtained instance then the isTransient() method returns true if the Instance injection point is a transient field, and false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 06:30:00 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Fri, 10 Jun 2016 06:30:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250776#comment-13250776 ] Mark Struberg commented on CDI-616: ----------------------------------- There are cases where it make sense. But actually only with method and ct injection points. In the first case we obviously need to store the info about the dependent bean in the enclosing CreationalContext {code} public class MySample { private MyBean mb; @Inject public setMe(MyBean mb) { this.mb = mb; } } {code} In the second example it makes perfect sense to mark the injection point as transient: {code} public class MySample { private OtherStuff os; @Inject public setMe(@TransientReference MyBean mb) { this.os = mb.createOtherStuff(); } } {code} > Injection point declared as transient is not useful > --------------------------------------------------- > > Key: CDI-616 > URL: https://issues.jboss.org/browse/CDI-616 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.2.Final > Environment: n/a > Reporter: Emily Jiang > Priority: Minor > > An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. > => > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. > Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 06:36:01 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 10 Jun 2016 06:36:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250781#comment-13250781 ] John Ament commented on CDI-616: -------------------------------- Are you referencing: {code} @Inject private transient Foo foo; {code} Or the {{@TransientReference}} from Mark? > Injection point declared as transient is not useful > --------------------------------------------------- > > Key: CDI-616 > URL: https://issues.jboss.org/browse/CDI-616 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.2.Final > Environment: n/a > Reporter: Emily Jiang > Priority: Minor > > An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. > => > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. > Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 09:49:00 2016 From: issues at jboss.org (Stephan Knitelius (JIRA)) Date: Fri, 10 Jun 2016 09:49:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250933#comment-13250933 ] Stephan Knitelius commented on CDI-616: --------------------------------------- I agree transient injects field injections are not useful. I have encountered several projects where IP where made transient because of FindBugs warnings. Maybe we should define a warning at startup when transient injection points are encountered. > Injection point declared as transient is not useful > --------------------------------------------------- > > Key: CDI-616 > URL: https://issues.jboss.org/browse/CDI-616 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.2.Final > Environment: n/a > Reporter: Emily Jiang > Priority: Minor > > An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. > => > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. > Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 09:56:00 2016 From: issues at jboss.org (Emily Jiang (JIRA)) Date: Fri, 10 Jun 2016 09:56:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-420) add a bean-discovery-mode 'scoped' In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250938#comment-13250938 ] Emily Jiang commented on CDI-420: --------------------------------- Martin, for implementing of Include, the scan process has to be changed. I do agree that your exclusion involves less changes. I think Martin's approach can do a finer-grain exclusion, on a package basis. e.g. If I have a jar containing some third party classes, org.apache.* plus in-house package com.abc.blah. I can exclude the classes without bean defining annotations from the package org.apache.* while I can include all classes from the package com.abc.blah. > add a bean-discovery-mode 'scoped' > ---------------------------------- > > Key: CDI-420 > URL: https://issues.jboss.org/browse/CDI-420 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: TBD > Reporter: Mark Struberg > Fix For: 2.0 (discussion) > > > This is for some future CDI release. > We currently only have 3 bean-discovery-modes > * none > * all > * annotated > The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for > ? each Java class, interface or enum deployed in an explicit bean archive, and > ? each Java class with a bean defining annotation in an implicit bean archive. > ? each session bean > Which means that we do not get the ProcessAnnotatedType (PAT) event for any class in an 'annotated' or 'implicit' BDA which does _not_ have a bean defining annotation. > It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them up as Beans if they (after PAT) do not have a valid scope. Effectively doing the processing but not make them @Dependent automatically if there is no scope annotation at the end of the PAT processing. > I'm not yet 100% sure how important this distinction is in practice. Just writing this up to not forget about the idea... -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 10 12:22:00 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Fri, 10 Jun 2016 12:22:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251059#comment-13251059 ] Mark Struberg commented on CDI-616: ----------------------------------- Are we talking about a real java 'transient' field? Of course adding transient to an injected CDI field is utter rubbish ^^. Or are we talking about InjectionPoint#isTransient() and the CDI @TransientReference annotation? That is the one I was basing my explanation on. > Injection point declared as transient is not useful > --------------------------------------------------- > > Key: CDI-616 > URL: https://issues.jboss.org/browse/CDI-616 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.2.Final > Environment: n/a > Reporter: Emily Jiang > Priority: Minor > > An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. > => > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. > Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Sun Jun 12 17:50:00 2016 From: issues at jboss.org (Emily Jiang (JIRA)) Date: Sun, 12 Jun 2016 17:50:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251237#comment-13251237 ] Emily Jiang commented on CDI-616: --------------------------------- Mark, we are talking about a real java "transient" field. Hence my suggestion of advising users not to use it or printing warnings as suggested by Stephan. > Injection point declared as transient is not useful > --------------------------------------------------- > > Key: CDI-616 > URL: https://issues.jboss.org/browse/CDI-616 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.2.Final > Environment: n/a > Reporter: Emily Jiang > Priority: Minor > > An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. > => > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. > Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Mon Jun 13 01:11:00 2016 From: issues at jboss.org (Mark Struberg (JIRA)) Date: Mon, 13 Jun 2016 01:11:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251257#comment-13251257 ] Mark Struberg commented on CDI-616: ----------------------------------- Indeed! Btw I looked a bit closer and @TransientReference can only be applied to parameters. So this is fine as well. Regarding transient fields. Could be useful to have non-normalscoped beans marked transient and manually resolve them from the BeanManager during deserialisation. This is perfectly legit. Some time ago I asked the Sonar guys to remove the non-serializable check for all @Inject fields: https://groups.google.com/forum/#!topic/sonarqube/6Q8uloyPj1w > Injection point declared as transient is not useful > --------------------------------------------------- > > Key: CDI-616 > URL: https://issues.jboss.org/browse/CDI-616 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.2.Final > Environment: n/a > Reporter: Emily Jiang > Priority: Minor > > An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. > => > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. > Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From antoine at sabot-durand.net Mon Jun 13 17:02:44 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Mon, 13 Jun 2016 21:02:44 +0000 Subject: [cdi-dev] Tomorrow's meeting on SE bootstrap Message-ID: Hi all, I'd like to focus tomorrow's meeting on SE bootstrap evolutions. I made some simplification on the Container interface and introduce a CDISE object to clearly remove SE feature (shutdown) from EE classes. Please take a look at https://github.com/cdi-spec/cdi/pull/290. to review API change (I'm still working on the spec part) Antoine -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160613/b58319db/attachment.html From john.d.ament at gmail.com Mon Jun 13 17:29:03 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Mon, 13 Jun 2016 21:29:03 +0000 Subject: [cdi-dev] Tomorrow's meeting on SE bootstrap In-Reply-To: References: Message-ID: I'd also like to understand if there are any issues remaining with https://github.com/cdi-spec/cdi/pull/291 and if not any blockers on pushing? On Mon, Jun 13, 2016 at 5:04 PM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: > Hi all, > > I'd like to focus tomorrow's meeting on SE bootstrap evolutions. > > I made some simplification on the Container interface and introduce a > CDISE object to clearly remove SE feature (shutdown) from EE classes. > > Please take a look at https://github.com/cdi-spec/cdi/pull/290. to review > API change (I'm still working on the spec part) > > Antoine > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160613/d597302c/attachment.html From tremes at redhat.com Tue Jun 14 03:45:53 2016 From: tremes at redhat.com (Tomas Remes) Date: Tue, 14 Jun 2016 03:45:53 -0400 (EDT) Subject: [cdi-dev] Tomorrow's meeting on SE bootstrap In-Reply-To: References: Message-ID: <1740532021.15129936.1465890353976.JavaMail.zimbra@redhat.com> John I think there are still some open questions without any answer so I think this would deserve some more discussion/attention. Tom ----- Original Message ----- From: "John D. Ament" To: "Antoine Sabot-Durand" , "cdi-dev" Sent: Monday, June 13, 2016 11:29:03 PM Subject: Re: [cdi-dev] Tomorrow's meeting on SE bootstrap I'd also like to understand if there are any issues remaining with https://github.com/cdi-spec/cdi/pull/291 and if not any blockers on pushing? On Mon, Jun 13, 2016 at 5:04 PM Antoine Sabot-Durand < antoine at sabot-durand.net > wrote: Hi all, I'd like to focus tomorrow's meeting on SE bootstrap evolutions. I made some simplification on the Container interface and introduce a CDISE object to clearly remove SE feature (shutdown) from EE classes. Please take a look at https://github.com/cdi-spec/cdi/pull/290 . to review API change (I'm still working on the spec part) Antoine _______________________________________________ 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. _______________________________________________ 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. From antoine at sabot-durand.net Tue Jun 14 03:51:35 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Tue, 14 Jun 2016 07:51:35 +0000 Subject: [cdi-dev] Tomorrow's meeting on SE bootstrap In-Reply-To: <1740532021.15129936.1465890353976.JavaMail.zimbra@redhat.com> References: <1740532021.15129936.1465890353976.JavaMail.zimbra@redhat.com> Message-ID: Perhaps it's necessary to plan an hangout meeting to discuss these points in f2f Antoine Le mar. 14 juin 2016 ? 09:45, Tomas Remes a ?crit : > > John I think there are still some open questions without any answer so I > think this would deserve some more discussion/attention. > > Tom > > ----- Original Message ----- > From: "John D. Ament" > To: "Antoine Sabot-Durand" , "cdi-dev" < > cdi-dev at lists.jboss.org> > Sent: Monday, June 13, 2016 11:29:03 PM > Subject: Re: [cdi-dev] Tomorrow's meeting on SE bootstrap > > I'd also like to understand if there are any issues remaining with > https://github.com/cdi-spec/cdi/pull/291 and if not any blockers on > pushing? > > On Mon, Jun 13, 2016 at 5:04 PM Antoine Sabot-Durand < > antoine at sabot-durand.net > wrote: > > > > Hi all, > > I'd like to focus tomorrow's meeting on SE bootstrap evolutions. > > I made some simplification on the Container interface and introduce a > CDISE object to clearly remove SE feature (shutdown) from EE classes. > > Please take a look at https://github.com/cdi-spec/cdi/pull/290 . to > review API change (I'm still working on the spec part) > > Antoine > _______________________________________________ > 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. > > _______________________________________________ > 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. > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160614/bb56b195/attachment-0001.html From john.d.ament at gmail.com Tue Jun 14 06:31:33 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Tue, 14 Jun 2016 10:31:33 +0000 Subject: [cdi-dev] Tomorrow's meeting on SE bootstrap In-Reply-To: References: <1740532021.15129936.1465890353976.JavaMail.zimbra@redhat.com> Message-ID: That may be easier. I'm representing this change as a compromise of what I understand the two very opposite opinions about how this should work are. May be best to discuss a bit more real time. In times matching you guys, I'm open Wednesday and Friday this week. Friday would be a little awkward as we're starting "summer hours" which means theres confusion over "real work" and "side stuff" but I think I can do it. Next week's not looking good until the end of the week. There's actually a good chance I'll have to miss next week's meeting, but am currently open Thursday/Friday. John On Tue, Jun 14, 2016 at 3:51 AM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: > Perhaps it's necessary to plan an hangout meeting to discuss these points > in f2f > > Antoine > > Le mar. 14 juin 2016 ? 09:45, Tomas Remes a ?crit : > >> >> John I think there are still some open questions without any answer so I >> think this would deserve some more discussion/attention. >> >> Tom >> >> ----- Original Message ----- >> From: "John D. Ament" >> To: "Antoine Sabot-Durand" , "cdi-dev" < >> cdi-dev at lists.jboss.org> >> Sent: Monday, June 13, 2016 11:29:03 PM >> Subject: Re: [cdi-dev] Tomorrow's meeting on SE bootstrap >> >> I'd also like to understand if there are any issues remaining with >> https://github.com/cdi-spec/cdi/pull/291 and if not any blockers on >> pushing? >> >> On Mon, Jun 13, 2016 at 5:04 PM Antoine Sabot-Durand < >> antoine at sabot-durand.net > wrote: >> >> >> >> Hi all, >> >> I'd like to focus tomorrow's meeting on SE bootstrap evolutions. >> >> I made some simplification on the Container interface and introduce a >> CDISE object to clearly remove SE feature (shutdown) from EE classes. >> >> Please take a look at https://github.com/cdi-spec/cdi/pull/290 . to >> review API change (I'm still working on the spec part) >> >> Antoine >> _______________________________________________ >> 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. >> >> _______________________________________________ >> 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. >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160614/ecab7355/attachment.html From issues at jboss.org Wed Jun 15 04:40:01 2016 From: issues at jboss.org (Emily Jiang (JIRA)) Date: Wed, 15 Jun 2016 04:40:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252647#comment-13252647 ] Emily Jiang commented on CDI-616: --------------------------------- Mark, although the transient dependent scoped bean injection point can be worked around, it is not as easy and simple as using @Inject Instance<>. > Injection point declared as transient is not useful > --------------------------------------------------- > > Key: CDI-616 > URL: https://issues.jboss.org/browse/CDI-616 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.2.Final > Environment: n/a > Reporter: Emily Jiang > Priority: Minor > > An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. > => > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. > Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 15 06:11:00 2016 From: issues at jboss.org (fabiola luice (JIRA)) Date: Wed, 15 Jun 2016 06:11:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-617) Instantly Ring @18oo-078.6054Norton technical support phone number, Norton customer service telephone number, In-Reply-To: References: Message-ID: fabiola luice created CDI-617: --------------------------------- Summary: Instantly Ring @18oo-078.6054Norton technical support phone number, Norton customer service telephone number, Key: CDI-617 URL: https://issues.jboss.org/browse/CDI-617 Project: CDI Specification Issues Issue Type: Bug Reporter: fabiola luice Instantly Ring @18oo-078.6054Norton technical support phone number, Norton customer service telephone number, Norton antivirus internert security phone number.pdf, 23.0 KB (added by moila, 24 seconds ago) Instantly Ring @18oo-078.6054Norton technical support phone number, Norton customer service telephone number, Norton antivirus internert security phone number USA !!(1.8005.456054)) !!Norton Technical Support Phone number(1.8oo.078.6054)Norton Customer support phone number @@Call, +1.8oo.078.6054 for all type help by Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number,@@@ Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number,@@@@ Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, @@@@@ Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number-Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number, Antivirus Norton Tech Support contact number, Antivirus Norton support contact number, Antivirus Norton technical support contact number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number. It is very popular toll free number which provide by Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number, Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number @@Call, +1.8oo.078.6054 for all type help by Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number,@@@ Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number,@@@@ Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, @@@@@ Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number-Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number, Antivirus Norton Tech Support contact number, Antivirus Norton support contact number, Antivirus Norton technical support contact number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number. It is very popular toll free number which provide by Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number, Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number @@Call, +1.8oo.078.6054 for all type help by Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number,@@@ Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number,@@@@ Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, @@@@@ Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number-Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number, Antivirus Norton Tech Support contact number, Antivirus Norton support contact number, Antivirus Norton technical support contact number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number. It is very popular toll free number which provide by Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number, Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number Norton antivirus phone number 1-8oo-078-6054 Norton antivirus customer service phone number 1-8oo-078-6054 Norton antivirus customer service billing Norton antivirus phone number 1-8oo-078-6054 Norton phone number cancel subscription 1-8oo-078-6054 Norton technical support phone number 1-8oo-078-6054 Norton 8oo phone number 1-8oo-078-6054 snapdeal toll free customer care number sbi toll free customer care number airtel toll free customer care number hdfc toll free customer care number bsnl toll free customer care number icici toll free customer care number flipkart toll free customer care number vodafone toll free customer care number Norton technical support phone number Norton technical support number Norton technical support number symantec technical support number Norton antivirus technical support number Norton locations Norton online support Norton billing phone number Norton customer care Norton tech support phone number Norton tech support phone number Norton antivirus tech support phone number Norton locations Norton billing phone number service Norton com Norton login Norton technical support phone number Norton customer service Norton billing phone number Norton support telephone number Norton support phone number Norton antivirus support phone number Norton support phone number Norton locations Norton customer service Norton customer care Norton billing phone number Norton customer support phone number Norton customer support phone number Norton antivirus customer support phone number Norton antivirus customer service phone number Norton antivirus technical support phone number Norton antivirus tech support phone number Norton antivirus phone number Norton security center phone number Norton support telephone number Norton 360 technical support phone number symantec technical support phone number Norton tech support phone number apple technical support phone number usa microsoft technical support phone number usa gmail technical support phone number usa Norton technical support phone number usa lenovo technical support phone number usa epson technical support phone number usa Norton technical support phone number call Norton support chat with Norton support Norton customer support Norton antivirus customer service number Norton address Norton call center Norton hq Norton office locations Norton support site Norton telephone number for customer support Norton customer service contact number Norton customer care Norton toll free number Norton security contact number contact Norton Norton headquarters Norton customer service chat Norton customer service telephone number Norton billing phone number Norton customer support Norton customer service refund Norton login Norton locations Norton customer service number uk Norton locations Norton customer service email address Norton support site Norton technical support phone number Norton technical support live chat Norton technical support email address Norton technical support number Norton technical support number symantec technical support number Norton antivirus technical support number Norton customer support phone number Norton customer support number Norton customer support number Norton antivirus customer support number Norton locations Norton billing phone number Norton corporate phone number Norton customer service billing Norton technical support phone number Norton tech support phone number Norton tech support number Norton tech support number -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 15 06:24:01 2016 From: issues at jboss.org (Martin Kouba (JIRA)) Date: Wed, 15 Jun 2016 06:24:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-617) Instantly Ring @18oo-078.6054Norton technical support phone number, Norton customer service telephone number, In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Kouba deleted CDI-617: ----------------------------- > Instantly Ring @18oo-078.6054Norton technical support phone number, Norton customer service telephone number, > --------------------------------------------------------------------------------------------------------------- > > Key: CDI-617 > URL: https://issues.jboss.org/browse/CDI-617 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: fabiola luice > > Instantly Ring @18oo-078.6054Norton technical support phone number, Norton customer service telephone number, > Norton antivirus internert security phone number.pdf, 23.0 KB (added by moila, 24 seconds ago) > Instantly Ring @18oo-078.6054Norton technical support phone number, Norton customer service telephone number, Norton antivirus internert security phone number USA !!(1.8005.456054)) !!Norton Technical Support Phone number(1.8oo.078.6054)Norton Customer support phone number @@Call, +1.8oo.078.6054 for all type help by Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number,@@@ Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number,@@@@ Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, @@@@@ Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number-Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number, Antivirus Norton Tech Support contact number, Antivirus Norton support contact number, Antivirus Norton technical support contact number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number. It is very popular toll free number which provide by Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number, Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number @@Call, +1.8oo.078.6054 for all type help by Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number,@@@ Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number,@@@@ Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, @@@@@ Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number-Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number, Antivirus Norton Tech Support contact number, Antivirus Norton support contact number, Antivirus Norton technical support contact number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number. It is very popular toll free number which provide by Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number, Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number @@Call, +1.8oo.078.6054 for all type help by Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number,@@@ Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number,@@@@ Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, @@@@@ Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number-Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number, Antivirus Norton Tech Support contact number, Antivirus Norton support contact number, Antivirus Norton technical support contact number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number. It is very popular toll free number which provide by Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number. Call, Antivirus Norton tech support phone number, Antivirus Norton Tech Support Phone Number, Antivirus Norton Help Desk Phone Number, Antivirus Norton tech support number, Antivirus Norton technical support phone number, Antivirus Norton phone number, Antivirus Norton technical support number, Antivirus Norton support phone number, Antivirus Norton technical support, Antivirus Norton Customer Service Phone Number, Antivirus Norton Customer Service Number, Antivirus Norton Customer Support Phone Number, Antivirus Norton Customer Support Number, Antivirus Norton Customer Service Helpline Number, Antivirus Norton Customer Care Number, Antivirus Norton support team phone number, Antivirus Norton help number-Antivirus Norton Helpline Number; Antivirus Norton help phone number, Antivirus Norton Helpline Number, Antivirus Norton Tech Support Toll free Number, Antivirus Norton Support Telephone Number, Antivirus Norton Tech Support Telephone number Norton antivirus phone number 1-8oo-078-6054 Norton antivirus customer service phone number 1-8oo-078-6054 Norton antivirus customer service billing Norton antivirus phone number 1-8oo-078-6054 Norton phone number cancel subscription 1-8oo-078-6054 Norton technical support phone number 1-8oo-078-6054 Norton 8oo phone number 1-8oo-078-6054 snapdeal toll free customer care number sbi toll free customer care number airtel toll free customer care number hdfc toll free customer care number bsnl toll free customer care number icici toll free customer care number flipkart toll free customer care number vodafone toll free customer care number Norton technical support phone number Norton technical support number Norton technical support number symantec technical support number Norton antivirus technical support number Norton locations Norton online support Norton billing phone number Norton customer care Norton tech support phone number Norton tech support phone number Norton antivirus tech support phone number Norton locations Norton billing phone number service Norton com Norton login Norton technical support phone number Norton customer service Norton billing phone number Norton support telephone number Norton support phone number Norton antivirus support phone number Norton support phone number Norton locations Norton customer service Norton customer care Norton billing phone number Norton customer support phone number Norton customer support phone number Norton antivirus customer support phone number Norton antivirus customer service phone number Norton antivirus technical support phone number Norton antivirus tech support phone number Norton antivirus phone number Norton security center phone number Norton support telephone number Norton 360 technical support phone number symantec technical support phone number Norton tech support phone number apple technical support phone number usa microsoft technical support phone number usa gmail technical support phone number usa Norton technical support phone number usa lenovo technical support phone number usa epson technical support phone number usa Norton technical support phone number call Norton support chat with Norton support Norton customer support Norton antivirus customer service number Norton address Norton call center Norton hq Norton office locations Norton support site Norton telephone number for customer support Norton customer service contact number Norton customer care Norton toll free number Norton security contact number contact Norton Norton headquarters Norton customer service chat Norton customer service telephone number Norton billing phone number Norton customer support Norton customer service refund Norton login Norton locations Norton customer service number uk Norton locations Norton customer service email address Norton support site Norton technical support phone number Norton technical support live chat Norton technical support email address Norton technical support number Norton technical support number symantec technical support number Norton antivirus technical support number Norton customer support phone number Norton customer support number Norton customer support number Norton antivirus customer support number Norton locations Norton billing phone number Norton corporate phone number Norton customer service billing Norton technical support phone number Norton tech support phone number Norton tech support number Norton tech support number -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Wed Jun 15 08:08:00 2016 From: issues at jboss.org (Stephan Knitelius (JIRA)) Date: Wed, 15 Jun 2016 08:08:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-616) Injection point declared as transient is not useful In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252810#comment-13252810 ] Stephan Knitelius commented on CDI-616: --------------------------------------- {quote} Regarding transient fields. Could be useful to have non-normalscoped beans marked transient and manually resolve them from the BeanManager during deserialisation. This is perfectly legit. {quote} [~struberg] are you sure, I can't think of (m)any resonalbe usecases? Never the less, my suggestion is: * ERROR - when normal scoped injects are marked transient. * WARNING - when non-normal scoped injects are marked transient. > Injection point declared as transient is not useful > --------------------------------------------------- > > Key: CDI-616 > URL: https://issues.jboss.org/browse/CDI-616 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.2.Final > Environment: n/a > Reporter: Emily Jiang > Priority: Minor > > An injection point declared as 'transient' is not useful, due to the fact of after bean's passivation, the transient field will not be reinjected and its value will be lost. This causes confusion. See Weld forum discussion [link title|https://developer.jboss.org/thread/179486]. In the section 5.5.7, how about to make the following changes? > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. > => > The isTransient() method returns true if the injection point is a transient field, and > false otherwise. If the injection point represents a dynamically obtained instance then the > isTransient() method returns true if the Instance injection point is a transient field, and > false otherwise. If this injection point is declared as transient, after bean's passivation, the value will not be restored. Instance injection point is the preferred approach. > Any other better suggestions? -- This message was sent by Atlassian JIRA (v6.4.11#64026) From antoine at sabot-durand.net Mon Jun 20 04:47:10 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Mon, 20 Jun 2016 08:47:10 +0000 Subject: [cdi-dev] New version for CDI bootstrap Message-ID: Hi guys, I posted modification on PR 290 [1] according to last meeting. I still have 2 points that stays open for me (you may have more) : - Place and name of the package: should we decide to package SE support in a specific jar, it will be probably better to have a better package name at a higher level - Name for CDISE class. Perhaps using Container or SeContainer would be better. WDYT ? Antoine [1] https://github.com/cdi-spec/cdi/pull/290 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160620/19a5b42d/attachment.html From rmannibucau at gmail.com Mon Jun 20 05:02:37 2016 From: rmannibucau at gmail.com (Romain Manni-Bucau) Date: Mon, 20 Jun 2016 11:02:37 +0200 Subject: [cdi-dev] New version for CDI bootstrap In-Reply-To: References: Message-ID: Hello Antoine, does it make sense to have close() and shutdown() in CDISE? Isn't close() enough? in findContainerBuilder: iterator shouldn't be called twice I think About naming: CDISE looks too much an anagram so maybe StandaloneCDI (I'd prefer "Standalone" to "SE") or even UserManagedCDI About packaging: ".standalone" is good enough IMO Romain Manni-Bucau @rmannibucau | Blog | Old Wordpress Blog | Github | LinkedIn | Tomitriber | JavaEE Factory 2016-06-20 10:47 GMT+02:00 Antoine Sabot-Durand : > Hi guys, > > I posted modification on PR 290 [1] according to last meeting. > > I still have 2 points that stays open for me (you may have more) : > > - Place and name of the package: should we decide to package SE support in > a specific jar, it will be probably better to have a better package name at > a higher level > > - Name for CDISE class. Perhaps using Container or SeContainer would be > better. WDYT ? > > Antoine > > [1] https://github.com/cdi-spec/cdi/pull/290 > > _______________________________________________ > 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160620/6847c386/attachment.html From john.d.ament at gmail.com Mon Jun 20 06:30:07 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Mon, 20 Jun 2016 10:30:07 +0000 Subject: [cdi-dev] New version for CDI bootstrap In-Reply-To: References: Message-ID: If your'e using container builder, I would call it "container" instead of CDISE. Even if we switch to initializer or configurator, this should become the container class. I'm in favor of this being its own spec jar, and really anything that is SE specific going there. If we end up with something that is web specific, we should consider moving that out as well. All other issues I see are commented in the PR. Looks like we're really close. I'm not going to be able to attend tomorrows meeting, unfortunately, but still wanted to see if we could coordinate a real time chat around CDI-30. John On Mon, Jun 20, 2016 at 4:48 AM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: > Hi guys, > > I posted modification on PR 290 [1] according to last meeting. > > I still have 2 points that stays open for me (you may have more) : > > - Place and name of the package: should we decide to package SE support in > a specific jar, it will be probably better to have a better package name at > a higher level > > - Name for CDISE class. Perhaps using Container or SeContainer would be > better. WDYT ? > > Antoine > > [1] https://github.com/cdi-spec/cdi/pull/290 > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160620/1ca7c380/attachment.html From mkouba at redhat.com Mon Jun 20 06:53:50 2016 From: mkouba at redhat.com (Martin Kouba) Date: Mon, 20 Jun 2016 12:53:50 +0200 Subject: [cdi-dev] New version for CDI bootstrap In-Reply-To: References: Message-ID: <5767CB3E.70108@redhat.com> Dne 20.6.2016 v 12:30 John D. Ament napsal(a): > If your'e using container builder, I would call it "container" instead > of CDISE. Even if we switch to initializer or configurator, this should > become the container class. Emily had a good point during mtg that the name Container is a bit overused (just try to open Container class in your IDE). So StandaloneContainer or CDIContainer or UserContainer might be a better choice... > > I'm in favor of this being its own spec jar, and really anything that is > SE specific going there. If we end up with something that is web > specific, we should consider moving that out as well. +1 > > All other issues I see are commented in the PR. Looks like we're really > close. > > I'm not going to be able to attend tomorrows meeting, unfortunately, but > still wanted to see if we could coordinate a real time chat around CDI-30. > > John > > On Mon, Jun 20, 2016 at 4:48 AM Antoine Sabot-Durand > > wrote: > > Hi guys, > > I posted modification on PR 290 [1] according to last meeting. > > I still have 2 points that stays open for me (you may have more) : > > - Place and name of the package: should we decide to package SE > support in a specific jar, it will be probably better to have a > better package name at a higher level > > - Name for CDISE class. Perhaps using Container or SeContainer > would be better. WDYT ? > > Antoine > > [1] https://github.com/cdi-spec/cdi/pull/290 > _______________________________________________ > 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. > > > > _______________________________________________ > 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. > -- Martin Kouba Software Engineer Red Hat, Czech Republic From antoine at sabot-durand.net Mon Jun 20 10:55:34 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Mon, 20 Jun 2016 14:55:34 +0000 Subject: [cdi-dev] CDI-30 hangout meeting Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160620/22b760d3/attachment-0001.html From struberg at yahoo.de Tue Jun 21 03:22:27 2016 From: struberg at yahoo.de (Mark Struberg) Date: Tue, 21 Jun 2016 09:22:27 +0200 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: References: Message-ID: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> 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 : > > 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 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. From mkouba at redhat.com Tue Jun 21 04:41:45 2016 From: mkouba at redhat.com (Martin Kouba) Date: Tue, 21 Jun 2016 10:41:45 +0200 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> References: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> Message-ID: <5768FDC9.8090203@redhat.com> 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 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 : >> >> 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 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. > > > _______________________________________________ > 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. > -- Martin Kouba Software Engineer Red Hat, Czech Republic From antoine at sabot-durand.net Tue Jun 21 10:13:24 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Tue, 21 Jun 2016 14:13:24 +0000 Subject: [cdi-dev] Canceling today's meeting Message-ID: Hi Guys, >From what I understand John and Mark won't be available for our meeting (correct me if I'm wrong). So perhaps we could postpone until the F2F meeting we'll have later this week to deal with open PR. BTW John could you give us your availability for such a meeting. Thx, Antoine -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/2d96546b/attachment.html From antoine at sabot-durand.net Tue Jun 21 10:20:17 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Tue, 21 Jun 2016 14:20:17 +0000 Subject: [cdi-dev] EDR2 release date and content Message-ID: Hi, As planned, I'd like to release EDR2 before end of July, so we should freeze API and spec around July 22nd (or before if possible). This EDR will demonstrate at least new configurator API and new SE Bootstrap. There are still open ticket on both features so we should concentrate our work on them. I don't reject other features (context control would be nice to have too), but I think we should @Inject the required work to finish these 2 features before adding others. Your feedback is welcome. Antoine -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/66c52130/attachment.html From john.d.ament at gmail.com Tue Jun 21 10:23:46 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Tue, 21 Jun 2016 14:23:46 +0000 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: <5768FDC9.8090203@redhat.com> References: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> <5768FDC9.8090203@redhat.com> Message-ID: 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 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 > > > 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 at 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 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. > > > > > > _______________________________________________ > > 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. > > > > -- > Martin Kouba > Software Engineer > Red Hat, Czech Republic > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/efc7e497/attachment.html From john.d.ament at gmail.com Tue Jun 21 10:26:01 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Tue, 21 Jun 2016 14:26:01 +0000 Subject: [cdi-dev] EDR2 release date and content In-Reply-To: References: Message-ID: Antoine, My understanding is that configuration is pretty much solid now. There's some things to potentially add, but the current version is working. Are there open issues? I would love to see context control in play for EDR2, its pretty important to users. John On Tue, Jun 21, 2016 at 10:20 AM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: > Hi, > > As planned, I'd like to release EDR2 before end of July, so we should > freeze API and spec around July 22nd (or before if possible). > > This EDR will demonstrate at least new configurator API and new SE > Bootstrap. There are still open ticket on both features so we should > concentrate our work on them. I don't reject other features (context > control would be nice to have too), but I think we should @Inject the > required work to finish these 2 features before adding others. > > Your feedback is welcome. > > Antoine > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/38b0fab2/attachment-0001.html From mkouba at redhat.com Tue Jun 21 10:27:10 2016 From: mkouba at redhat.com (Martin Kouba) Date: Tue, 21 Jun 2016 16:27:10 +0200 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: References: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> <5768FDC9.8090203@redhat.com> Message-ID: <57694EBE.5090300@redhat.com> 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 > 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 > > > 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 > >: > >> > >> 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 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. > > > > > > _______________________________________________ > > 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. > > > > -- > Martin Kouba > Software Engineer > Red Hat, Czech Republic > _______________________________________________ > 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. > -- Martin Kouba Software Engineer Red Hat, Czech Republic From john.d.ament at gmail.com Tue Jun 21 10:35:09 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Tue, 21 Jun 2016 14:35:09 +0000 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: <57694EBE.5090300@redhat.com> References: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> <5768FDC9.8090203@redhat.com> <57694EBE.5090300@redhat.com> Message-ID: 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 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 > > 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 > > > > > > 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 > > >: > > >> > > >> 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 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. > > > > > > > > > _______________________________________________ > > > 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. > > > > > > > -- > > Martin Kouba > > Software Engineer > > Red Hat, Czech Republic > > _______________________________________________ > > 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. > > > > -- > 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/500a5977/attachment.html From antoine at sabot-durand.net Tue Jun 21 10:41:31 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Tue, 21 Jun 2016 14:41:31 +0000 Subject: [cdi-dev] EDR2 release date and content In-Reply-To: References: Message-ID: Same for me John. We have 1 month to do it right. I think it's reachable. Antoine Le mar. 21 juin 2016 ? 16:26, John D. Ament a ?crit : > Antoine, > > My understanding is that configuration is pretty much solid now. There's > some things to potentially add, but the current version is working. Are > there open issues? > > I would love to see context control in play for EDR2, its pretty important > to users. > > John > > On Tue, Jun 21, 2016 at 10:20 AM Antoine Sabot-Durand < > antoine at sabot-durand.net> wrote: > >> Hi, >> >> As planned, I'd like to release EDR2 before end of July, so we should >> freeze API and spec around July 22nd (or before if possible). >> >> This EDR will demonstrate at least new configurator API and new SE >> Bootstrap. There are still open ticket on both features so we should >> concentrate our work on them. I don't reject other features (context >> control would be nice to have too), but I think we should @Inject the >> required work to finish these 2 features before adding others. >> >> Your feedback is welcome. >> >> Antoine >> > _______________________________________________ >> 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/ac3496df/attachment-0001.html From antoine at sabot-durand.net Tue Jun 21 11:13:54 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Tue, 21 Jun 2016 15:13:54 +0000 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: References: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> <5768FDC9.8090203@redhat.com> <57694EBE.5090300@redhat.com> Message-ID: 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 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 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 > > > 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 >> > >> > >> > 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 >> > >: >> > >> >> > >> 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 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. >> > > >> > > >> > > _______________________________________________ >> > > 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. >> > > >> > >> > -- >> > Martin Kouba >> > Software Engineer >> > Red Hat, Czech Republic >> > _______________________________________________ >> > 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. >> > >> >> -- >> 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.html From john.d.ament at gmail.com Tue Jun 21 11:16:23 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Tue, 21 Jun 2016 11:16:23 -0400 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: References: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> <5768FDC9.8090203@redhat.com> <57694EBE.5090300@redhat.com> Message-ID: Monday is better for me but I can do both. On Jun 21, 2016 11:14, "Antoine Sabot-Durand" 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 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 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 >> > > 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 >>> > >>> > >>> > 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 >>> > >: >>> > >> >>> > >> 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 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. >>> > > >>> > > >>> > > _______________________________________________ >>> > > 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. >>> > > >>> > >>> > -- >>> > Martin Kouba >>> > Software Engineer >>> > Red Hat, Czech Republic >>> > _______________________________________________ >>> > 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. >>> > >>> >>> -- >>> 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-0001.html From mkouba at redhat.com Tue Jun 21 11:28:42 2016 From: mkouba at redhat.com (Martin Kouba) Date: Tue, 21 Jun 2016 17:28:42 +0200 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: References: <519B6F9A-18CF-4F0C-BFB7-97DC53795869@yahoo.de> <5768FDC9.8090203@redhat.com> <57694EBE.5090300@redhat.com> Message-ID: <57695D2A.7050900@redhat.com> Dne 21.6.2016 v 16:35 John D. Ament napsal(a): > 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. I'm sorry but I still don't understand this concept. From what I understand a context may be associated with one or more threads. But a thread cannot have more than one associated contexts for a certain scope. At least this is how it works now. And I believe this is implicitly defined in the spec, e.g. in 6.3. Normal scopes and pseudo-scopes: "The context associated with the current thread is called the current context for the scope." If more associated contexts were allowed it wouldn't be possible to distinguish the current context... > - 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) What does it mean "bridge from existing"? > > John > > On Tue, Jun 21, 2016 at 10:27 AM Martin Kouba > 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 > > >> 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 > > > > > > 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 > > > >>: > > >> > > >> 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 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. > > > > > > > > > _______________________________________________ > > > 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. > > > > > > > -- > > Martin Kouba > > Software Engineer > > Red Hat, Czech Republic > > _______________________________________________ > > 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. > > > > -- > Martin Kouba > Software Engineer > Red Hat, Czech Republic > -- Martin Kouba Software Engineer Red Hat, Czech Republic From werner.keil at gmail.com Tue Jun 21 11:31:31 2016 From: werner.keil at gmail.com (Werner Keil) Date: Tue, 21 Jun 2016 17:31:31 +0200 Subject: [cdi-dev] CDI-30 hangout meeting Message-ID: 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, wrote: > Send cdi-dev mailing list submissions to > cdi-dev at lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request at lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner at lists.jboss.org > > 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 > Subject: Re: [cdi-dev] CDI-30 hangout meeting > To: "John D. Ament" , Martin Kouba > , Mark Struberg > Cc: cdi-dev > Message-ID: > z1n2gjQ at mail.gmail.com> > 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 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 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 >> > > 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 > >> > > >> > > >> > 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 > >> > >: > >> > >> > >> > >> 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 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. > >> > > > >> > > > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > >> > -- > >> > Martin Kouba > >> > Software Engineer > >> > Red Hat, Czech Republic > >> > _______________________________________________ > >> > 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. > >> > > >> > >> -- > >> 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 > > ------------------------------ > > Message: 2 > Date: Tue, 21 Jun 2016 11:16:23 -0400 > From: "John D. Ament" > Subject: Re: [cdi-dev] CDI-30 hangout meeting > To: Antoine Sabot-Durand > Cc: cdi-dev at lists.jboss.org > Message-ID: > < > CAOqetn_3uk-WxjhT438TFueB3_fYnXQfmw+NHpFrZ2BZ3ZJBXw at mail.gmail.com> > 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" > 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 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 > 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 >>> > > 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 > >>> > > >>> > > >>> > 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 > >>> > >: > >>> > >> > >>> > >> 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 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. > >>> > > > >>> > > > >>> > > _______________________________________________ > >>> > > 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. > >>> > > > >>> > > >>> > -- > >>> > Martin Kouba > >>> > Software Engineer > >>> > Red Hat, Czech Republic > >>> > _______________________________________________ > >>> > 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. > >>> > > >>> > >>> -- > >>> 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 > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 12 > *************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/c7ed4a30/attachment-0001.html From EMIJIANG at uk.ibm.com Tue Jun 21 12:22:13 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Tue, 21 Jun 2016 17:22:13 +0100 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: References: Message-ID: 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: Werner Keil To: cdi-dev , Date: 21/06/2016 16:33 Subject: Re: [cdi-dev] CDI-30 hangout meeting Sent by: cdi-dev-bounces at 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, wrote: Send cdi-dev mailing list submissions to cdi-dev at lists.jboss.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.jboss.org/mailman/listinfo/cdi-dev or, via email, send a message with subject or body 'help' to cdi-dev-request at lists.jboss.org You can reach the person managing the list at cdi-dev-owner at lists.jboss.org 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 Subject: Re: [cdi-dev] CDI-30 hangout meeting To: "John D. Ament" , Martin Kouba , Mark Struberg Cc: cdi-dev Message-ID: 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 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 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 > > > 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 >> > >> > >> > 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 >> > >: >> > >> >> > >> 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 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. >> > > >> > > >> > > _______________________________________________ >> > > 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. >> > > >> > >> > -- >> > Martin Kouba >> > Software Engineer >> > Red Hat, Czech Republic >> > _______________________________________________ >> > 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. >> > >> >> -- >> 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 ------------------------------ Message: 2 Date: Tue, 21 Jun 2016 11:16:23 -0400 From: "John D. Ament" Subject: Re: [cdi-dev] CDI-30 hangout meeting To: Antoine Sabot-Durand Cc: cdi-dev at lists.jboss.org Message-ID: < CAOqetn_3uk-WxjhT438TFueB3_fYnXQfmw+NHpFrZ2BZ3ZJBXw at mail.gmail.com> 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" 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 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 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 >> > > 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 >>> > >>> > >>> > 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 >>> > >: >>> > >> >>> > >> 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 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. >>> > > >>> > > >>> > > _______________________________________________ >>> > > 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. >>> > > >>> > >>> > -- >>> > Martin Kouba >>> > Software Engineer >>> > Red Hat, Czech Republic >>> > _______________________________________________ >>> > 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. >>> > >>> >>> -- >>> 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 ------------------------------ _______________________________________________ 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. End of cdi-dev Digest, Vol 67, Issue 12 *************************************** _______________________________________________ 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/268e7a90/attachment-0001.html From john.d.ament at gmail.com Tue Jun 21 17:04:45 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Tue, 21 Jun 2016 21:04:45 +0000 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: References: Message-ID: 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 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: Werner Keil > To: cdi-dev , > Date: 21/06/2016 16:33 > Subject: Re: [cdi-dev] CDI-30 hangout meeting > Sent by: cdi-dev-bounces at 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 at lists.jboss.org* > > wrote: > Send cdi-dev mailing list submissions to > *cdi-dev at lists.jboss.org* > > To subscribe or unsubscribe via the World Wide Web, visit > *https://lists.jboss.org/mailman/listinfo/cdi-dev* > > or, via email, send a message with subject or body 'help' to > *cdi-dev-request at lists.jboss.org* > > > You can reach the person managing the list at > *cdi-dev-owner at lists.jboss.org* > > 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 at sabot-durand.net* > > > Subject: Re: [cdi-dev] CDI-30 hangout meeting > To: "John D. Ament" <*john.d.ament at gmail.com* >, > Martin Kouba > <*mkouba at redhat.com* >, Mark Struberg < > *struberg at yahoo.de* > > Cc: cdi-dev <*cdi-dev at lists.jboss.org* > > Message-ID: > *z1n2gjQ at mail.gmail.com* > > 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 at gmail.com* > > 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 at redhat.com* > > 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 at 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 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* > > >> > > >> > > >> > 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 at sabot-durand.net* *antoine at 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 at lists.jboss.org* *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. > >> > > > >> > > > >> > > _______________________________________________ > >> > > cdi-dev mailing list > >> > > *cdi-dev at lists.jboss.org* *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. > >> > > > >> > > >> > -- > >> > Martin Kouba > >> > Software Engineer > >> > Red Hat, Czech Republic > >> > _______________________________________________ > >> > cdi-dev mailing list > >> > *cdi-dev at lists.jboss.org* *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. > >> > > >> > >> -- > >> 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* > > > ------------------------------ > > Message: 2 > Date: Tue, 21 Jun 2016 11:16:23 -0400 > From: "John D. Ament" <*john.d.ament at gmail.com* > > Subject: Re: [cdi-dev] CDI-30 hangout meeting > To: Antoine Sabot-Durand <*antoine at sabot-durand.net* > > > Cc: *cdi-dev at lists.jboss.org* > Message-ID: > < > *CAOqetn_3uk-WxjhT438TFueB3_fYnXQfmw+NHpFrZ2BZ3ZJBXw at mail.gmail.com* > > > 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 at sabot-durand.net* > > > 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 at gmail.com* > > 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 at redhat.com* > > 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 at 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 > 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* > > >>> > > >>> > > >>> > 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 at sabot-durand.net* *antoine at 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 at lists.jboss.org* *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. > >>> > > > >>> > > > >>> > > _______________________________________________ > >>> > > cdi-dev mailing list > >>> > > *cdi-dev at lists.jboss.org* *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. > >>> > > > >>> > > >>> > -- > >>> > Martin Kouba > >>> > Software Engineer > >>> > Red Hat, Czech Republic > >>> > _______________________________________________ > >>> > cdi-dev mailing list > >>> > *cdi-dev at lists.jboss.org* *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. > >>> > > >>> > >>> -- > >>> 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* > > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 12 > *************************************** > _______________________________________________ > 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. > > > 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 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. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160621/29a93986/attachment-0001.html From antoine at sabot-durand.net Wed Jun 22 05:00:53 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Wed, 22 Jun 2016 09:00:53 +0000 Subject: [cdi-dev] CDI-30 hangout meeting In-Reply-To: References: Message-ID: Majority is for Friday so let's do this on Friday. I send an invitation to all people on this thread and on PR discussion. Antoine Le mar. 21 juin 2016 ? 23:05, John D. Ament a ?crit : > 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 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 at uk.ibm.com >> Lotus Notes: Emily Jiang/UK/IBM at IBMGB >> >> >> >> >> From: Werner Keil >> To: cdi-dev , >> Date: 21/06/2016 16:33 >> Subject: Re: [cdi-dev] CDI-30 hangout meeting >> Sent by: cdi-dev-bounces at 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 at lists.jboss.org* >> > wrote: >> Send cdi-dev mailing list submissions to >> *cdi-dev at lists.jboss.org* >> >> To subscribe or unsubscribe via the World Wide Web, visit >> *https://lists.jboss.org/mailman/listinfo/cdi-dev* >> >> or, via email, send a message with subject or body 'help' to >> *cdi-dev-request at lists.jboss.org* >> >> >> You can reach the person managing the list at >> *cdi-dev-owner at lists.jboss.org* >> >> 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 at sabot-durand.net* >> > >> Subject: Re: [cdi-dev] CDI-30 hangout meeting >> To: "John D. Ament" <*john.d.ament at gmail.com* >, >> Martin Kouba >> <*mkouba at redhat.com* >, Mark Struberg < >> *struberg at yahoo.de* > >> Cc: cdi-dev <*cdi-dev at lists.jboss.org* > >> Message-ID: >> > *z1n2gjQ at mail.gmail.com* > >> 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 at gmail.com* >> > 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 at redhat.com* >> > 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 at 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 >> 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* >> >> >> > >> >> > >> >> > 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 at sabot-durand.net* > *antoine at 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 at lists.jboss.org* > *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. >> >> > > >> >> > > >> >> > > _______________________________________________ >> >> > > cdi-dev mailing list >> >> > > *cdi-dev at lists.jboss.org* > *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. >> >> > > >> >> > >> >> > -- >> >> > Martin Kouba >> >> > Software Engineer >> >> > Red Hat, Czech Republic >> >> > _______________________________________________ >> >> > cdi-dev mailing list >> >> > *cdi-dev at lists.jboss.org* > *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. >> >> > >> >> >> >> -- >> >> 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* >> >> >> ------------------------------ >> >> Message: 2 >> Date: Tue, 21 Jun 2016 11:16:23 -0400 >> From: "John D. Ament" <*john.d.ament at gmail.com* > >> Subject: Re: [cdi-dev] CDI-30 hangout meeting >> To: Antoine Sabot-Durand <*antoine at sabot-durand.net* >> > >> Cc: *cdi-dev at lists.jboss.org* >> Message-ID: >> < >> *CAOqetn_3uk-WxjhT438TFueB3_fYnXQfmw+NHpFrZ2BZ3ZJBXw at mail.gmail.com* >> > >> 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 at sabot-durand.net* >> > >> 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 at gmail.com* >> > 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 at redhat.com* >> > 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 at 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 >> 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* >> >> >>> > >> >>> > >> >>> > 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 at sabot-durand.net* > *antoine at 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 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. >> >>> > > >> >>> > > >> >>> > > _______________________________________________ >> >>> > > cdi-dev mailing list >> >>> > > *cdi-dev at lists.jboss.org* > *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. >> >>> > > >> >>> > >> >>> > -- >> >>> > Martin Kouba >> >>> > Software Engineer >> >>> > Red Hat, Czech Republic >> >>> > _______________________________________________ >> >>> > cdi-dev mailing list >> >>> > *cdi-dev at lists.jboss.org* > *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. >> >>> > >> >>> >> >>> -- >> >>> 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* >> >> >> ------------------------------ >> >> _______________________________________________ >> 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. >> >> End of cdi-dev Digest, Vol 67, Issue 12 >> *************************************** >> _______________________________________________ >> 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. >> >> >> 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 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. >> > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160622/4ac4b9a1/attachment-0001.html From antoine at sabot-durand.net Thu Jun 23 06:05:47 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Thu, 23 Jun 2016 10:05:47 +0000 Subject: [cdi-dev] Please review PR 290 (bootstrap se) Message-ID: Hi all, After integration of feedback, the new bootstrap API is in its final form. Please review it carefully to find the possible last errors [1]. Generated spec doc can also be read here [2] Thanks for your help to integrate this very expected feature. Antoine [1] https://github.com/cdi-spec/cdi/pull/290 [2] https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/c20da341/attachment.html From john.d.ament at gmail.com Thu Jun 23 06:08:50 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Thu, 23 Jun 2016 10:08:50 +0000 Subject: [cdi-dev] Please review PR 290 (bootstrap se) In-Reply-To: References: Message-ID: Antoine, Did you go a little too deep in renaming container -> bootstrap? Looks like many references to an EE container were changed. Intentional? John On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: > Hi all, > > After integration of feedback, the new bootstrap API is in its final form. > Please review it carefully to find the possible last errors [1]. > > Generated spec doc can also be read here [2] > > Thanks for your help to integrate this very expected feature. > > > Antoine > > > > [1] https://github.com/cdi-spec/cdi/pull/290 > [2] https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/2951cec1/attachment.html From antoine at sabot-durand.net Thu Jun 23 07:06:49 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Thu, 23 Jun 2016 11:06:49 +0000 Subject: [cdi-dev] Please review PR 290 (bootstrap se) In-Reply-To: References: Message-ID: OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let me correct this Le jeu. 23 juin 2016 ? 12:09, John D. Ament a ?crit : > Antoine, > > Did you go a little too deep in renaming container -> bootstrap? Looks > like many references to an EE container were changed. Intentional? > > John > > On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < > antoine at sabot-durand.net> wrote: > >> Hi all, >> >> After integration of feedback, the new bootstrap API is in its final form. >> Please review it carefully to find the possible last errors [1]. >> >> Generated spec doc can also be read here [2] >> >> Thanks for your help to integrate this very expected feature. >> >> >> Antoine >> >> >> >> [1] https://github.com/cdi-spec/cdi/pull/290 >> [2] >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se >> > _______________________________________________ >> 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/18dabf29/attachment.html From antoine at sabot-durand.net Thu Jun 23 07:47:50 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Thu, 23 Jun 2016 11:47:50 +0000 Subject: [cdi-dev] Please review PR 290 (bootstrap se) In-Reply-To: References: Message-ID: Error corrected. You can review the PR Thx John Le jeu. 23 juin 2016 ? 13:06, Antoine Sabot-Durand a ?crit : > OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let > me correct this > > Le jeu. 23 juin 2016 ? 12:09, John D. Ament a > ?crit : > >> Antoine, >> >> Did you go a little too deep in renaming container -> bootstrap? Looks >> like many references to an EE container were changed. Intentional? >> >> John >> >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < >> antoine at sabot-durand.net> wrote: >> >>> Hi all, >>> >>> After integration of feedback, the new bootstrap API is in its final >>> form. >>> Please review it carefully to find the possible last errors [1]. >>> >>> Generated spec doc can also be read here [2] >>> >>> Thanks for your help to integrate this very expected feature. >>> >>> >>> Antoine >>> >>> >>> >>> [1] https://github.com/cdi-spec/cdi/pull/290 >>> [2] >>> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se >>> >> _______________________________________________ >>> 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. >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/012c2a42/attachment.html From john.d.ament at gmail.com Thu Jun 23 08:01:21 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Thu, 23 Jun 2016 12:01:21 +0000 Subject: [cdi-dev] Updated PR 291 Message-ID: All, I've updated PR 291 with the open comments as much as possible, as a precursor to tomorrow's meeting. https://github.com/cdi-spec/cdi/pull/291 John -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/99a455fb/attachment.html From antoine at sabot-durand.net Thu Jun 23 16:37:42 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Thu, 23 Jun 2016 20:37:42 +0000 Subject: [cdi-dev] Tomorrow's meeting recording Message-ID: Hi all, As all of us won't be able to attend the meeting, it will be recorder for further reference. Hence the meeting will take place on redhat Bluejeans meeting service. II've just added the url to the invitation. If you want to attend and are not on the list please tell me and I'll add you. Antoine -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/9176249a/attachment-0001.html From john.d.ament at gmail.com Thu Jun 23 19:24:43 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Thu, 23 Jun 2016 23:24:43 +0000 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: Message-ID: Unfortunately, I won't be able to do video if its being recorded, too high risk of something written on a wall ending up on video. John On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: > Hi all, > > As all of us won't be able to attend the meeting, it will be recorder for > further reference. Hence the meeting will take place on redhat Bluejeans > meeting service. > II've just added the url to the invitation. > If you want to attend and are not on the list please tell me and I'll add > you. > > Antoine > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment.html From mkouba at redhat.com Fri Jun 24 03:06:16 2016 From: mkouba at redhat.com (Martin Kouba) Date: Fri, 24 Jun 2016 09:06:16 +0200 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: Message-ID: <576CDBE8.1040506@redhat.com> I should admit that it was my idea because I will not be able to attend the meeting and would really like to see/hear the discussion and arguments. Also I belive the recording should only be available to CDI EG memebers. Martin Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > Unfortunately, I won't be able to do video if its being recorded, too > high risk of something written on a wall ending up on video. > > John > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > > wrote: > > Hi all, > > As all of us won't be able to attend the meeting, it will be > recorder for further reference. Hence the meeting will take place on > redhat Bluejeans meeting service. > II've just added the url to the invitation. > If you want to attend and are not on the list please tell me and > I'll add you. > > Antoine > _______________________________________________ > 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. > > > > _______________________________________________ > 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. > -- Martin Kouba Software Engineer Red Hat, Czech Republic From antoine at sabot-durand.net Fri Jun 24 04:33:06 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Fri, 24 Jun 2016 08:33:06 +0000 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: <576CDBE8.1040506@redhat.com> References: <576CDBE8.1040506@redhat.com> Message-ID: It will have restricted access and will be destroyed with the merge of CDI-30 ;) Le ven. 24 juin 2016 ? 09:06, Martin Kouba a ?crit : > I should admit that it was my idea because I will not be able to attend > the meeting and would really like to see/hear the discussion and arguments. > > Also I belive the recording should only be available to CDI EG memebers. > > Martin > > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > > Unfortunately, I won't be able to do video if its being recorded, too > > high risk of something written on a wall ending up on video. > > > > John > > > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > > > wrote: > > > > Hi all, > > > > As all of us won't be able to attend the meeting, it will be > > recorder for further reference. Hence the meeting will take place on > > redhat Bluejeans meeting service. > > II've just added the url to the invitation. > > If you want to attend and are not on the list please tell me and > > I'll add you. > > > > Antoine > > _______________________________________________ > > 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. > > > > > > > > _______________________________________________ > > 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. > > > > -- > Martin Kouba > Software Engineer > Red Hat, Czech Republic > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment.html From mjremijan at yahoo.com Fri Jun 24 08:58:07 2016 From: mjremijan at yahoo.com (Michael Remijan) Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) Subject: [cdi-dev] Please review PR 290 (bootstrap se) In-Reply-To: References: Message-ID: <2064584222.725169.1466773087613.JavaMail.yahoo@mail.yahoo.com> Is a build available yet to test the new Bootstrap? I'd like to upgrade from 3.0.0.Alpha15 On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand wrote: Error corrected. You can review the PR Thx John Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand a ?crit?: OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let me correct this Le?jeu. 23 juin 2016 ??12:09, John D. Ament a ?crit?: Antoine, Did you go a little too deep in renaming container -> bootstrap? Looks like many references to an EE container were changed.? Intentional? John On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand wrote: Hi all, After integration of feedback, the new bootstrap API is in its final form.Please review it carefully to find the possible last errors [1]. Generated spec doc can also be read here [2] Thanks for your help to integrate this very expected feature. Antoine [1] https://github.com/cdi-spec/cdi/pull/290 [2] https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se _______________________________________________ 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. _______________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment-0001.html From werner.keil at gmail.com Fri Jun 24 09:01:44 2016 From: werner.keil at gmail.com (Werner Keil) Date: Fri, 24 Jun 2016 15:01:44 +0200 Subject: [cdi-dev] Tomorrow's meeting recording Message-ID: >...too high >risk of something written on a wall ending up on video. So much for transparency;-| Werner On Fri, Jun 24, 2016 at 2:59 PM, wrote: > Send cdi-dev mailing list submissions to > cdi-dev at lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request at lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner at lists.jboss.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. Re: Tomorrow's meeting recording (John D. Ament) > 2. Re: Tomorrow's meeting recording (Martin Kouba) > 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) > 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 23 Jun 2016 23:24:43 +0000 > From: "John D. Ament" > Subject: Re: [cdi-dev] Tomorrow's meeting recording > To: Antoine Sabot-Durand , cdi-dev > > Message-ID: > < > CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Unfortunately, I won't be able to do video if its being recorded, too high > risk of something written on a wall ending up on video. > > John > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < > antoine at sabot-durand.net> wrote: > > > Hi all, > > > > As all of us won't be able to attend the meeting, it will be recorder for > > further reference. Hence the meeting will take place on redhat Bluejeans > > meeting service. > > II've just added the url to the invitation. > > If you want to attend and are not on the list please tell me and I'll add > > you. > > > > Antoine > > _______________________________________________ > > 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. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Fri, 24 Jun 2016 09:06:16 +0200 > From: Martin Kouba > Subject: Re: [cdi-dev] Tomorrow's meeting recording > To: "John D. Ament" , Antoine Sabot-Durand > , cdi-dev > Message-ID: <576CDBE8.1040506 at redhat.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > I should admit that it was my idea because I will not be able to attend > the meeting and would really like to see/hear the discussion and arguments. > > Also I belive the recording should only be available to CDI EG memebers. > > Martin > > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > > Unfortunately, I won't be able to do video if its being recorded, too > > high risk of something written on a wall ending up on video. > > > > John > > > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > > > wrote: > > > > Hi all, > > > > As all of us won't be able to attend the meeting, it will be > > recorder for further reference. Hence the meeting will take place on > > redhat Bluejeans meeting service. > > II've just added the url to the invitation. > > If you want to attend and are not on the list please tell me and > > I'll add you. > > > > Antoine > > _______________________________________________ > > 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. > > > > > > > > _______________________________________________ > > 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. > > > > -- > Martin Kouba > Software Engineer > Red Hat, Czech Republic > > > ------------------------------ > > Message: 3 > Date: Fri, 24 Jun 2016 08:33:06 +0000 > From: Antoine Sabot-Durand > Subject: Re: [cdi-dev] Tomorrow's meeting recording > To: Martin Kouba , "John D. Ament" > , cdi-dev > Message-ID: > < > CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > It will have restricted access and will be destroyed with the merge of > CDI-30 ;) > > Le ven. 24 juin 2016 ? 09:06, Martin Kouba a ?crit : > > > I should admit that it was my idea because I will not be able to attend > > the meeting and would really like to see/hear the discussion and > arguments. > > > > Also I belive the recording should only be available to CDI EG memebers. > > > > Martin > > > > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > > > Unfortunately, I won't be able to do video if its being recorded, too > > > high risk of something written on a wall ending up on video. > > > > > > John > > > > > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > > > > wrote: > > > > > > Hi all, > > > > > > As all of us won't be able to attend the meeting, it will be > > > recorder for further reference. Hence the meeting will take place > on > > > redhat Bluejeans meeting service. > > > II've just added the url to the invitation. > > > If you want to attend and are not on the list please tell me and > > > I'll add you. > > > > > > Antoine > > > _______________________________________________ > > > 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. > > > > > > > > > > > > _______________________________________________ > > > 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. > > > > > > > -- > > Martin Kouba > > Software Engineer > > Red Hat, Czech Republic > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html > > ------------------------------ > > Message: 4 > Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) > From: Michael Remijan > Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) > To: Antoine Sabot-Durand , "John D. Ament" > , cdi-dev > Message-ID: > <2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com> > Content-Type: text/plain; charset="utf-8" > > Is a build available yet to test the new Bootstrap? I'd like to upgrade > from 3.0.0.Alpha15 > > > > On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < > antoine at sabot-durand.net> wrote: > > > Error corrected. You can review the PR > Thx John > Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < > antoine at sabot-durand.net> a ?crit?: > > OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let > me correct this > Le?jeu. 23 juin 2016 ??12:09, John D. Ament a > ?crit?: > > Antoine, > Did you go a little too deep in renaming container -> bootstrap? Looks > like many references to an EE container were changed.? Intentional? > John > On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < > antoine at sabot-durand.net> wrote: > > Hi all, > After integration of feedback, the new bootstrap API is in its final > form.Please review it carefully to find the possible last errors [1]. > Generated spec doc can also be read here [2] > Thanks for your help to integrate this very expected feature. > > Antoine > > > [1] https://github.com/cdi-spec/cdi/pull/290 > [2] https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > > _______________________________________________ > 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. > > > > _______________________________________________ > 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. > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 18 > *************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/a58ec9bc/attachment-0001.html From john.d.ament at gmail.com Fri Jun 24 09:14:09 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Fri, 24 Jun 2016 13:14:09 +0000 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: Message-ID: On Fri, Jun 24, 2016 at 9:02 AM Werner Keil wrote: > >...too high > >risk of something written on a wall ending up on video. > > So much for transparency;-| > Werner, are you concerned that my employer is not being transparent about internal R&D items to outside parties? > > Werner > > > On Fri, Jun 24, 2016 at 2:59 PM, wrote: > >> Send cdi-dev mailing list submissions to >> cdi-dev at lists.jboss.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.jboss.org/mailman/listinfo/cdi-dev >> or, via email, send a message with subject or body 'help' to >> cdi-dev-request at lists.jboss.org >> >> You can reach the person managing the list at >> cdi-dev-owner at lists.jboss.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of cdi-dev digest..." >> >> >> Today's Topics: >> >> 1. Re: Tomorrow's meeting recording (John D. Ament) >> 2. Re: Tomorrow's meeting recording (Martin Kouba) >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 23 Jun 2016 23:24:43 +0000 >> From: "John D. Ament" >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: Antoine Sabot-Durand , cdi-dev >> >> Message-ID: >> < >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" > > >> >> Unfortunately, I won't be able to do video if its being recorded, too high >> risk of something written on a wall ending up on video. >> >> John >> >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < >> > antoine at sabot-durand.net> wrote: >> >> > Hi all, >> > >> > As all of us won't be able to attend the meeting, it will be recorder >> for >> > further reference. Hence the meeting will take place on redhat Bluejeans >> > meeting service. >> > II've just added the url to the invitation. >> > If you want to attend and are not on the list please tell me and I'll >> add >> > you. >> > >> > Antoine >> > _______________________________________________ >> > 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. >> > -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html >> >> ------------------------------ >> >> Message: 2 >> Date: Fri, 24 Jun 2016 09:06:16 +0200 >> From: Martin Kouba >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: "John D. Ament" , Antoine Sabot-Durand >> , cdi-dev >> Message-ID: <576CDBE8.1040506 at redhat.com> >> Content-Type: text/plain; charset=windows-1252; format=flowed > > >> >> I should admit that it was my idea because I will not be able to attend >> the meeting and would really like to see/hear the discussion and >> arguments. >> >> Also I belive the recording should only be available to CDI EG memebers. >> >> Martin >> >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): >> > Unfortunately, I won't be able to do video if its being recorded, too >> > high risk of something written on a wall ending up on video. >> > >> > John >> > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand >> > > wrote: >> > >> > Hi all, >> > >> > As all of us won't be able to attend the meeting, it will be >> > recorder for further reference. Hence the meeting will take place on >> > redhat Bluejeans meeting service. >> > II've just added the url to the invitation. >> > If you want to attend and are not on the list please tell me and >> > I'll add you. >> > >> > Antoine >> > _______________________________________________ >> > 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. >> > >> > >> > >> > _______________________________________________ >> > 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. >> > >> >> -- >> Martin Kouba >> Software Engineer >> Red Hat, Czech Republic >> >> >> ------------------------------ >> >> Message: 3 >> Date: Fri, 24 Jun 2016 08:33:06 +0000 >> From: Antoine Sabot-Durand >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: Martin Kouba , "John D. Ament" >> , cdi-dev >> Message-ID: >> < >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" > > >> >> It will have restricted access and will be destroyed with the merge of >> CDI-30 ;) >> >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba a ?crit : > > >> >> > I should admit that it was my idea because I will not be able to attend >> > the meeting and would really like to see/hear the discussion and >> arguments. >> > >> > Also I belive the recording should only be available to CDI EG memebers. >> > >> > Martin >> > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): >> > > Unfortunately, I won't be able to do video if its being recorded, too >> > > high risk of something written on a wall ending up on video. >> > > >> > > John >> > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand >> > > > wrote: >> > > >> > > Hi all, >> > > >> > > As all of us won't be able to attend the meeting, it will be >> > > recorder for further reference. Hence the meeting will take place >> on >> > > redhat Bluejeans meeting service. >> > > II've just added the url to the invitation. >> > > If you want to attend and are not on the list please tell me and >> > > I'll add you. >> > > >> > > Antoine >> > > _______________________________________________ >> > > 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. >> > > >> > > >> > > >> > > _______________________________________________ >> > > 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. >> > > >> > >> > -- >> > Martin Kouba >> > Software Engineer >> > Red Hat, Czech Republic >> > >> > -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html >> >> ------------------------------ >> >> Message: 4 >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) >> From: Michael Remijan >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) >> To: Antoine Sabot-Durand , "John D. Ament" >> , cdi-dev >> Message-ID: >> <2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com> >> Content-Type: text/plain; charset="utf-8" >> >> Is a build available yet to test the new Bootstrap? I'd like to upgrade >> from 3.0.0.Alpha15 >> >> >> >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < >> antoine at sabot-durand.net> wrote: >> >> >> Error corrected. You can review the PR >> Thx John >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < >> antoine at sabot-durand.net> a ?crit?: >> >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let >> me correct this >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament a >> ?crit?: >> >> Antoine, >> Did you go a little too deep in renaming container -> bootstrap? Looks >> like many references to an EE container were changed.? Intentional? >> John > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < >> antoine at sabot-durand.net> wrote: >> >> Hi all, >> > After integration of feedback, the new bootstrap API is in its final >> form.Please review it carefully to find the possible last errors [1]. >> Generated spec doc can also be read here [2] >> Thanks for your help to integrate this very expected feature. >> >> Antoine >> >> >> [1] https://github.com/cdi-spec/cdi/pull/290 >> [2] >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > >> >> >> _______________________________________________ >> 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. >> >> >> >> _______________________________________________ >> 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. >> >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html >> >> ------------------------------ > > >> >> _______________________________________________ >> 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. >> >> End of cdi-dev Digest, Vol 67, Issue 18 >> *************************************** >> > > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment-0001.html From werner.keil at gmail.com Fri Jun 24 09:19:26 2016 From: werner.keil at gmail.com (Werner Keil) Date: Fri, 24 Jun 2016 15:19:26 +0200 Subject: [cdi-dev] Tomorrow's meeting recording Message-ID: Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not the only participant or EG sometimes lacking transparency. I would not even be able to join the hangout here at the client's office simply because there's no working audio HW in our laptops, not so much because of what's on the walls behind me (generally they are also extremely secretive, but there is nothing behind my desk that would unveil secrets;-) Werner On Fri, Jun 24, 2016 at 3:14 PM, wrote: > Send cdi-dev mailing list submissions to > cdi-dev at lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request at lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner at lists.jboss.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. Re: Tomorrow's meeting recording (John D. Ament) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 24 Jun 2016 13:14:09 +0000 > From: "John D. Ament" > Subject: Re: [cdi-dev] Tomorrow's meeting recording > To: Werner Keil , cdi-dev > > Message-ID: > 6cAE5hGbOFY-MPq+pFWQScSOBCoPCt3guop+hnQ at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Fri, Jun 24, 2016 at 9:02 AM Werner Keil wrote: > > > >...too high > > >risk of something written on a wall ending up on video. > > > > So much for transparency;-| > > > > Werner, are you concerned that my employer is not being transparent about > internal R&D items to outside parties? > > > > > > Werner > > > > > > On Fri, Jun 24, 2016 at 2:59 PM, > wrote: > > > >> Send cdi-dev mailing list submissions to > >> cdi-dev at lists.jboss.org > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> https://lists.jboss.org/mailman/listinfo/cdi-dev > >> or, via email, send a message with subject or body 'help' to > >> cdi-dev-request at lists.jboss.org > >> > >> You can reach the person managing the list at > >> cdi-dev-owner at lists.jboss.org > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of cdi-dev digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: Tomorrow's meeting recording (John D. Ament) > >> 2. Re: Tomorrow's meeting recording (Martin Kouba) > >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) > >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) > >> > >> > >> ---------------------------------------------------------------------- > >> > >> Message: 1 > >> Date: Thu, 23 Jun 2016 23:24:43 +0000 > >> From: "John D. Ament" > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Antoine Sabot-Durand , cdi-dev > >> > >> Message-ID: > >> < > >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com> > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> Unfortunately, I won't be able to do video if its being recorded, too > high > >> risk of something written on a wall ending up on video. > >> > >> John > >> > >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < > >> > > antoine at sabot-durand.net> wrote: > >> > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be recorder > >> for > >> > further reference. Hence the meeting will take place on redhat > Bluejeans > >> > meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and I'll > >> add > >> > you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html > >> > >> ------------------------------ > >> > >> Message: 2 > >> Date: Fri, 24 Jun 2016 09:06:16 +0200 > >> From: Martin Kouba > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: "John D. Ament" , Antoine Sabot-Durand > >> , cdi-dev < > cdi-dev at lists.jboss.org> > >> Message-ID: <576CDBE8.1040506 at redhat.com> > >> Content-Type: text/plain; charset=windows-1252; format=flowed > > > > > >> > >> I should admit that it was my idea because I will not be able to attend > >> the meeting and would really like to see/hear the discussion and > >> arguments. > >> > >> Also I belive the recording should only be available to CDI EG memebers. > >> > >> Martin > >> > >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > Unfortunately, I won't be able to do video if its being recorded, too > >> > high risk of something written on a wall ending up on video. > >> > > >> > John > >> > > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > > wrote: > >> > > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be > >> > recorder for further reference. Hence the meeting will take place > on > >> > redhat Bluejeans meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and > >> > I'll add you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > >> > > >> > > >> > _______________________________________________ > >> > 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. > >> > > >> > >> -- > >> Martin Kouba > >> Software Engineer > >> Red Hat, Czech Republic > >> > >> > >> ------------------------------ > >> > >> Message: 3 > >> Date: Fri, 24 Jun 2016 08:33:06 +0000 > >> From: Antoine Sabot-Durand > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Martin Kouba , "John D. Ament" > >> , cdi-dev < > cdi-dev at lists.jboss.org> > >> Message-ID: > >> < > >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com> > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> It will have restricted access and will be destroyed with the merge of > >> CDI-30 ;) > >> > >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba a ?crit > : > > > > > >> > >> > I should admit that it was my idea because I will not be able to > attend > >> > the meeting and would really like to see/hear the discussion and > >> arguments. > >> > > >> > Also I belive the recording should only be available to CDI EG > memebers. > >> > > >> > Martin > >> > > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > > Unfortunately, I won't be able to do video if its being recorded, > too > >> > > high risk of something written on a wall ending up on video. > >> > > > >> > > John > >> > > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > > > wrote: > >> > > > >> > > Hi all, > >> > > > >> > > As all of us won't be able to attend the meeting, it will be > >> > > recorder for further reference. Hence the meeting will take > place > >> on > >> > > redhat Bluejeans meeting service. > >> > > II've just added the url to the invitation. > >> > > If you want to attend and are not on the list please tell me and > >> > > I'll add you. > >> > > > >> > > Antoine > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > > >> > > > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > >> > -- > >> > Martin Kouba > >> > Software Engineer > >> > Red Hat, Czech Republic > >> > > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html > >> > >> ------------------------------ > >> > >> Message: 4 > >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) > >> From: Michael Remijan > >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) > >> To: Antoine Sabot-Durand , "John D. Ament" > >> , cdi-dev > >> Message-ID: > >> <2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com> > >> Content-Type: text/plain; charset="utf-8" > >> > >> Is a build available yet to test the new Bootstrap? I'd like to upgrade > >> from 3.0.0.Alpha15 > >> > >> > >> > >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < > >> antoine at sabot-durand.net> wrote: > >> > >> > >> Error corrected. You can review the PR > >> Thx John > >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < > >> antoine at sabot-durand.net> a ?crit?: > >> > >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. > Let > >> me correct this > >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament a > >> ?crit?: > >> > >> Antoine, > >> Did you go a little too deep in renaming container -> bootstrap? Looks > >> like many references to an EE container were changed.? Intentional? > >> John > > > > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < > >> antoine at sabot-durand.net> wrote: > >> > >> Hi all, > >> > > After integration of feedback, the new bootstrap API is in its final > >> form.Please review it carefully to find the possible last errors [1]. > >> Generated spec doc can also be read here [2] > >> Thanks for your help to integrate this very expected feature. > >> > >> Antoine > >> > >> > >> [1] https://github.com/cdi-spec/cdi/pull/290 > >> [2] > >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > > > > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html > >> > >> ------------------------------ > > > > > >> > >> _______________________________________________ > >> 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. > >> > >> End of cdi-dev Digest, Vol 67, Issue 18 > >> *************************************** > >> > > > > _______________________________________________ > > 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. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 20 > *************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/e77f0305/attachment-0001.html From john.d.ament at gmail.com Fri Jun 24 09:28:02 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Fri, 24 Jun 2016 13:28:02 +0000 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: Message-ID: On Fri, Jun 24, 2016 at 9:19 AM Werner Keil wrote: > Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not > the only participant or EG sometimes lacking transparency. I would not even > be able to join the hangout here at the client's office simply because > there's no working audio HW in our laptops, not so much because of what's > on the walls behind me (generally they are also extremely secretive, but > there is nothing behind my desk that would unveil secrets;-) > We have white board walls instead of rolling boards, so there's always something written on a wall somewhere. Here's an example: https://s-media-cache-ak0.pinimg.com/236x/77/41/0d/77410de3f8040c5edf6e613e10e11e93.jpg John > > Werner > > > On Fri, Jun 24, 2016 at 3:14 PM, wrote: > >> Send cdi-dev mailing list submissions to >> cdi-dev at lists.jboss.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.jboss.org/mailman/listinfo/cdi-dev >> or, via email, send a message with subject or body 'help' to >> cdi-dev-request at lists.jboss.org >> >> You can reach the person managing the list at >> cdi-dev-owner at lists.jboss.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of cdi-dev digest..." >> >> >> Today's Topics: >> >> 1. Re: Tomorrow's meeting recording (John D. Ament) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 24 Jun 2016 13:14:09 +0000 > > >> From: "John D. Ament" >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> > To: Werner Keil , cdi-dev >> >> Message-ID: >> > 6cAE5hGbOFY-MPq+pFWQScSOBCoPCt3guop+hnQ at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" > > >> >> On Fri, Jun 24, 2016 at 9:02 AM Werner Keil >> wrote: >> >> > >...too high >> > >risk of something written on a wall ending up on video. >> > >> > So much for transparency;-| >> > >> >> Werner, are you concerned that my employer is not being transparent about >> internal R&D items to outside parties? >> >> >> > >> > Werner >> > >> > >> > On Fri, Jun 24, 2016 at 2:59 PM, >> wrote: >> > >> >> Send cdi-dev mailing list submissions to >> >> cdi-dev at lists.jboss.org >> >> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> >> https://lists.jboss.org/mailman/listinfo/cdi-dev >> >> or, via email, send a message with subject or body 'help' to >> >> cdi-dev-request at lists.jboss.org >> >> >> >> You can reach the person managing the list at >> >> cdi-dev-owner at lists.jboss.org >> >> >> >> When replying, please edit your Subject line so it is more specific >> >> than "Re: Contents of cdi-dev digest..." >> >> >> >> >> >> Today's Topics: >> >> >> >> 1. Re: Tomorrow's meeting recording (John D. Ament) >> >> 2. Re: Tomorrow's meeting recording (Martin Kouba) >> >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) >> >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) >> >> >> >> >> >> ---------------------------------------------------------------------- >> >> >> >> Message: 1 >> >> Date: Thu, 23 Jun 2016 23:24:43 +0000 >> >> From: "John D. Ament" >> >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> >> To: Antoine Sabot-Durand , cdi-dev >> >> >> >> Message-ID: >> >> < >> >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com> >> >> Content-Type: text/plain; charset="utf-8" >> > >> > >> >> >> >> Unfortunately, I won't be able to do video if its being recorded, too >> high >> >> risk of something written on a wall ending up on video. >> >> >> >> John >> >> >> >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < >> >> >> > antoine at sabot-durand.net> wrote: >> >> >> >> > Hi all, >> >> > >> >> > As all of us won't be able to attend the meeting, it will be recorder >> >> for >> >> > further reference. Hence the meeting will take place on redhat >> Bluejeans >> >> > meeting service. >> >> > II've just added the url to the invitation. >> >> > If you want to attend and are not on the list please tell me and I'll >> >> add >> >> > you. >> >> > >> >> > Antoine >> >> > _______________________________________________ >> >> > 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. >> >> >> > -------------- next part -------------- >> >> An HTML attachment was scrubbed... >> >> URL: >> >> >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html >> >> >> >> ------------------------------ >> >> >> >> Message: 2 >> >> Date: Fri, 24 Jun 2016 09:06:16 +0200 >> >> From: Martin Kouba >> >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> >> To: "John D. Ament" , Antoine Sabot-Durand >> >> , cdi-dev < >> cdi-dev at lists.jboss.org> >> >> Message-ID: <576CDBE8.1040506 at redhat.com> >> >> Content-Type: text/plain; charset=windows-1252; format=flowed >> > >> > >> >> >> >> I should admit that it was my idea because I will not be able to attend >> >> the meeting and would really like to see/hear the discussion and >> >> arguments. >> >> >> >> Also I belive the recording should only be available to CDI EG >> memebers. >> >> >> >> Martin >> >> >> >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): >> >> > Unfortunately, I won't be able to do video if its being recorded, too >> >> > high risk of something written on a wall ending up on video. >> >> > >> >> > John >> >> > >> >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand >> >> > > wrote: >> >> > >> >> > Hi all, >> >> > >> >> > As all of us won't be able to attend the meeting, it will be >> >> > recorder for further reference. Hence the meeting will take >> place on >> >> > redhat Bluejeans meeting service. >> >> > II've just added the url to the invitation. >> >> > If you want to attend and are not on the list please tell me and >> >> > I'll add you. >> >> > >> >> > Antoine >> >> > _______________________________________________ >> >> > 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. >> >> > >> >> > >> >> > >> >> > _______________________________________________ >> >> > 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. >> >> > >> >> >> >> -- >> >> Martin Kouba >> >> Software Engineer >> >> Red Hat, Czech Republic >> >> >> >> >> >> ------------------------------ >> >> >> >> Message: 3 >> >> Date: Fri, 24 Jun 2016 08:33:06 +0000 >> >> From: Antoine Sabot-Durand >> >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> >> To: Martin Kouba , "John D. Ament" >> >> , cdi-dev < >> cdi-dev at lists.jboss.org> >> >> Message-ID: >> >> < >> >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com> >> >> Content-Type: text/plain; charset="utf-8" >> > >> > >> >> >> >> It will have restricted access and will be destroyed with the merge of >> >> CDI-30 ;) >> >> >> >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba a >> ?crit : >> > >> > >> >> >> >> > I should admit that it was my idea because I will not be able to >> attend >> >> > the meeting and would really like to see/hear the discussion and >> >> arguments. >> >> > >> >> > Also I belive the recording should only be available to CDI EG >> memebers. >> >> > >> >> > Martin >> >> > >> >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): >> >> > > Unfortunately, I won't be able to do video if its being recorded, >> too >> >> > > high risk of something written on a wall ending up on video. >> >> > > >> >> > > John >> >> > > >> >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand >> >> > > > >> wrote: >> >> > > >> >> > > Hi all, >> >> > > >> >> > > As all of us won't be able to attend the meeting, it will be >> >> > > recorder for further reference. Hence the meeting will take >> place >> >> on >> >> > > redhat Bluejeans meeting service. >> >> > > II've just added the url to the invitation. >> >> > > If you want to attend and are not on the list please tell me >> and >> >> > > I'll add you. >> >> > > >> >> > > Antoine >> >> > > _______________________________________________ >> >> > > 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. >> >> > > >> >> > > >> >> > > >> >> > > _______________________________________________ >> >> > > 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. >> >> > > >> >> > >> >> > -- >> >> > Martin Kouba >> >> > Software Engineer >> >> > Red Hat, Czech Republic >> >> > >> >> >> > -------------- next part -------------- >> >> An HTML attachment was scrubbed... >> >> URL: >> >> >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html >> >> >> >> ------------------------------ >> >> >> >> Message: 4 >> >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) >> >> From: Michael Remijan >> >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) >> >> To: Antoine Sabot-Durand , "John D. >> Ament" >> >> , cdi-dev >> >> Message-ID: >> >> <2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com >> > >> >> Content-Type: text/plain; charset="utf-8" >> >> >> >> Is a build available yet to test the new Bootstrap? I'd like to upgrade >> >> from 3.0.0.Alpha15 >> >> >> >> >> >> >> >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < >> >> antoine at sabot-durand.net> wrote: >> >> >> >> >> >> Error corrected. You can review the PR >> >> Thx John >> >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < >> >> antoine at sabot-durand.net> a ?crit?: >> >> >> >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. >> Let >> >> me correct this >> >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament a >> >> ?crit?: >> >> >> >> Antoine, >> >> Did you go a little too deep in renaming container -> bootstrap? Looks >> >> like many references to an EE container were changed.? Intentional? >> >> John >> > >> > >> >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < >> >> antoine at sabot-durand.net> wrote: >> >> >> >> Hi all, >> >> >> > After integration of feedback, the new bootstrap API is in its final >> >> form.Please review it carefully to find the possible last errors [1]. >> >> Generated spec doc can also be read here [2] >> >> Thanks for your help to integrate this very expected feature. >> >> >> >> Antoine >> >> >> >> >> >> [1] https://github.com/cdi-spec/cdi/pull/290 >> >> [2] >> >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se >> > >> > >> >> >> >> >> >> _______________________________________________ >> >> 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. >> >> >> >> >> >> >> >> _______________________________________________ >> >> 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. >> >> >> >> >> >> -------------- next part -------------- >> >> An HTML attachment was scrubbed... >> >> URL: >> > >> >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html >> >> >> >> ------------------------------ >> > >> > >> >> >> >> _______________________________________________ >> >> 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. >> >> >> > >> End of cdi-dev Digest, Vol 67, Issue 18 >> >> *************************************** >> >> >> > >> > _______________________________________________ >> > 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. >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> > URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html > > >> >> ------------------------------ >> >> _______________________________________________ >> 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. >> >> End of cdi-dev Digest, Vol 67, Issue 20 >> *************************************** >> > > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/32edd927/attachment-0001.html From EMIJIANG at uk.ibm.com Fri Jun 24 12:02:18 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Fri, 24 Jun 2016 17:02:18 +0100 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: Message-ID: Is the meeting on? I'm on requesting to join the video call... nothing happened 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: "John D. Ament" To: Werner Keil , cdi-dev , Date: 24/06/2016 14:29 Subject: Re: [cdi-dev] Tomorrow's meeting recording Sent by: cdi-dev-bounces at lists.jboss.org On Fri, Jun 24, 2016 at 9:19 AM Werner Keil wrote: Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not the only participant or EG sometimes lacking transparency. I would not even be able to join the hangout here at the client's office simply because there's no working audio HW in our laptops, not so much because of what's on the walls behind me (generally they are also extremely secretive, but there is nothing behind my desk that would unveil secrets;-) We have white board walls instead of rolling boards, so there's always something written on a wall somewhere. Here's an example: https://s-media-cache-ak0.pinimg.com/236x/77/41/0d/77410de3f8040c5edf6e613e10e11e93.jpg John Werner On Fri, Jun 24, 2016 at 3:14 PM, wrote: Send cdi-dev mailing list submissions to cdi-dev at lists.jboss.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.jboss.org/mailman/listinfo/cdi-dev or, via email, send a message with subject or body 'help' to cdi-dev-request at lists.jboss.org You can reach the person managing the list at cdi-dev-owner at lists.jboss.org When replying, please edit your Subject line so it is more specific than "Re: Contents of cdi-dev digest..." Today's Topics: 1. Re: Tomorrow's meeting recording (John D. Ament) ---------------------------------------------------------------------- Message: 1 Date: Fri, 24 Jun 2016 13:14:09 +0000 From: "John D. Ament" Subject: Re: [cdi-dev] Tomorrow's meeting recording To: Werner Keil , cdi-dev Message-ID: Content-Type: text/plain; charset="utf-8" On Fri, Jun 24, 2016 at 9:02 AM Werner Keil wrote: > >...too high > >risk of something written on a wall ending up on video. > > So much for transparency;-| > Werner, are you concerned that my employer is not being transparent about internal R&D items to outside parties? > > Werner > > > On Fri, Jun 24, 2016 at 2:59 PM, wrote: > >> Send cdi-dev mailing list submissions to >> cdi-dev at lists.jboss.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.jboss.org/mailman/listinfo/cdi-dev >> or, via email, send a message with subject or body 'help' to >> cdi-dev-request at lists.jboss.org >> >> You can reach the person managing the list at >> cdi-dev-owner at lists.jboss.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of cdi-dev digest..." >> >> >> Today's Topics: >> >> 1. Re: Tomorrow's meeting recording (John D. Ament) >> 2. Re: Tomorrow's meeting recording (Martin Kouba) >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 23 Jun 2016 23:24:43 +0000 >> From: "John D. Ament" >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: Antoine Sabot-Durand , cdi-dev >> >> Message-ID: >> < >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" > > >> >> Unfortunately, I won't be able to do video if its being recorded, too high >> risk of something written on a wall ending up on video. >> >> John >> >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < >> > antoine at sabot-durand.net> wrote: >> >> > Hi all, >> > >> > As all of us won't be able to attend the meeting, it will be recorder >> for >> > further reference. Hence the meeting will take place on redhat Bluejeans >> > meeting service. >> > II've just added the url to the invitation. >> > If you want to attend and are not on the list please tell me and I'll >> add >> > you. >> > >> > Antoine >> > _______________________________________________ >> > 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. >> > -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html >> >> ------------------------------ >> >> Message: 2 >> Date: Fri, 24 Jun 2016 09:06:16 +0200 >> From: Martin Kouba >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: "John D. Ament" , Antoine Sabot-Durand >> , cdi-dev < cdi-dev at lists.jboss.org> >> Message-ID: <576CDBE8.1040506 at redhat.com> >> Content-Type: text/plain; charset=windows-1252; format=flowed > > >> >> I should admit that it was my idea because I will not be able to attend >> the meeting and would really like to see/hear the discussion and >> arguments. >> >> Also I belive the recording should only be available to CDI EG memebers. >> >> Martin >> >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): >> > Unfortunately, I won't be able to do video if its being recorded, too >> > high risk of something written on a wall ending up on video. >> > >> > John >> > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand >> > > wrote: >> > >> > Hi all, >> > >> > As all of us won't be able to attend the meeting, it will be >> > recorder for further reference. Hence the meeting will take place on >> > redhat Bluejeans meeting service. >> > II've just added the url to the invitation. >> > If you want to attend and are not on the list please tell me and >> > I'll add you. >> > >> > Antoine >> > _______________________________________________ >> > 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. >> > >> > >> > >> > _______________________________________________ >> > 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. >> > >> >> -- >> Martin Kouba >> Software Engineer >> Red Hat, Czech Republic >> >> >> ------------------------------ >> >> Message: 3 >> Date: Fri, 24 Jun 2016 08:33:06 +0000 >> From: Antoine Sabot-Durand >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: Martin Kouba , "John D. Ament" >> , cdi-dev < cdi-dev at lists.jboss.org> >> Message-ID: >> < >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" > > >> >> It will have restricted access and will be destroyed with the merge of >> CDI-30 ;) >> >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba a ?crit : > > >> >> > I should admit that it was my idea because I will not be able to attend >> > the meeting and would really like to see/hear the discussion and >> arguments. >> > >> > Also I belive the recording should only be available to CDI EG memebers. >> > >> > Martin >> > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): >> > > Unfortunately, I won't be able to do video if its being recorded, too >> > > high risk of something written on a wall ending up on video. >> > > >> > > John >> > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand >> > > > wrote: >> > > >> > > Hi all, >> > > >> > > As all of us won't be able to attend the meeting, it will be >> > > recorder for further reference. Hence the meeting will take place >> on >> > > redhat Bluejeans meeting service. >> > > II've just added the url to the invitation. >> > > If you want to attend and are not on the list please tell me and >> > > I'll add you. >> > > >> > > Antoine >> > > _______________________________________________ >> > > 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. >> > > >> > > >> > > >> > > _______________________________________________ >> > > 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. >> > > >> > >> > -- >> > Martin Kouba >> > Software Engineer >> > Red Hat, Czech Republic >> > >> > -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html >> >> ------------------------------ >> >> Message: 4 >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) >> From: Michael Remijan >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) >> To: Antoine Sabot-Durand , "John D. Ament" >> , cdi-dev >> Message-ID: >> <2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com> >> Content-Type: text/plain; charset="utf-8" >> >> Is a build available yet to test the new Bootstrap? I'd like to upgrade >> from 3.0.0.Alpha15 >> >> >> >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < >> antoine at sabot-durand.net> wrote: >> >> >> Error corrected. You can review the PR >> Thx John >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < >> antoine at sabot-durand.net> a ?crit?: >> >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let >> me correct this >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament a >> ?crit?: >> >> Antoine, >> Did you go a little too deep in renaming container -> bootstrap? Looks >> like many references to an EE container were changed.? Intentional? >> John > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < >> antoine at sabot-durand.net> wrote: >> >> Hi all, >> > After integration of feedback, the new bootstrap API is in its final >> form.Please review it carefully to find the possible last errors [1]. >> Generated spec doc can also be read here [2] >> Thanks for your help to integrate this very expected feature. >> >> Antoine >> >> >> [1] https://github.com/cdi-spec/cdi/pull/290 >> [2] >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > >> >> >> _______________________________________________ >> 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. >> >> >> >> _______________________________________________ >> 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. >> >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html >> >> ------------------------------ > > >> >> _______________________________________________ >> 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. >> >> End of cdi-dev Digest, Vol 67, Issue 18 >> *************************************** >> > > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html ------------------------------ _______________________________________________ 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. End of cdi-dev Digest, Vol 67, Issue 20 *************************************** _______________________________________________ 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. _______________________________________________ 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/6247f66a/attachment-0001.html From john.d.ament at gmail.com Fri Jun 24 12:21:01 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Fri, 24 Jun 2016 16:21:01 +0000 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: Message-ID: Yes it is. On Fri, Jun 24, 2016 at 12:02 PM Emily Jiang wrote: > Is the meeting on? I'm on requesting to join the video call... nothing > happened > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: "John D. Ament" > To: Werner Keil , cdi-dev < > cdi-dev at lists.jboss.org>, > Date: 24/06/2016 14:29 > Subject: Re: [cdi-dev] Tomorrow's meeting recording > Sent by: cdi-dev-bounces at lists.jboss.org > ------------------------------ > > > > > > On Fri, Jun 24, 2016 at 9:19 AM Werner Keil <*werner.keil at gmail.com* > > wrote: > Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not > the only participant or EG sometimes lacking transparency. I would not even > be able to join the hangout here at the client's office simply because > there's no working audio HW in our laptops, not so much because of what's > on the walls behind me (generally they are also extremely secretive, but > there is nothing behind my desk that would unveil secrets;-) > > > We have white board walls instead of rolling boards, so there's always > something written on a wall somewhere. > > Here's an example: > *https://s-media-cache-ak0.pinimg.com/236x/77/41/0d/77410de3f8040c5edf6e613e10e11e93.jpg* > > > John > > > Werner > > > > On Fri, Jun 24, 2016 at 3:14 PM, <*cdi-dev-request at lists.jboss.org* > > wrote: > Send cdi-dev mailing list submissions to > *cdi-dev at lists.jboss.org* > > To subscribe or unsubscribe via the World Wide Web, visit > *https://lists.jboss.org/mailman/listinfo/cdi-dev* > > or, via email, send a message with subject or body 'help' to > *cdi-dev-request at lists.jboss.org* > > > You can reach the person managing the list at > *cdi-dev-owner at lists.jboss.org* > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. Re: Tomorrow's meeting recording (John D. Ament) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 24 Jun 2016 13:14:09 +0000 > > From: "John D. Ament" <*john.d.ament at gmail.com* > > Subject: Re: [cdi-dev] Tomorrow's meeting recording > To: Werner Keil <*werner.keil at gmail.com* >, cdi-dev > <*cdi-dev at lists.jboss.org* > > Message-ID: > *6cAE5hGbOFY-MPq+pFWQScSOBCoPCt3guop+hnQ at mail.gmail.com* > <6cAE5hGbOFY-MPq%2BpFWQScSOBCoPCt3guop%2BhnQ at mail.gmail.com>> > Content-Type: text/plain; charset="utf-8" > > > On Fri, Jun 24, 2016 at 9:02 AM Werner Keil <*werner.keil at gmail.com* > > wrote: > > > >...too high > > >risk of something written on a wall ending up on video. > > > > So much for transparency;-| > > > > Werner, are you concerned that my employer is not being transparent about > internal R&D items to outside parties? > > > > > > Werner > > > > > > On Fri, Jun 24, 2016 at 2:59 PM, <*cdi-dev-request at lists.jboss.org* > > wrote: > > > >> Send cdi-dev mailing list submissions to > >> *cdi-dev at lists.jboss.org* > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> *https://lists.jboss.org/mailman/listinfo/cdi-dev* > > >> or, via email, send a message with subject or body 'help' to > >> *cdi-dev-request at lists.jboss.org* > > >> > >> You can reach the person managing the list at > >> *cdi-dev-owner at lists.jboss.org* > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of cdi-dev digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: Tomorrow's meeting recording (John D. Ament) > >> 2. Re: Tomorrow's meeting recording (Martin Kouba) > >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) > >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) > >> > >> > >> ---------------------------------------------------------------------- > >> > >> Message: 1 > >> Date: Thu, 23 Jun 2016 23:24:43 +0000 > >> From: "John D. Ament" <*john.d.ament at gmail.com* > > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Antoine Sabot-Durand <*antoine at sabot-durand.net* > >, cdi-dev > >> <*cdi-dev at lists.jboss.org* > > >> Message-ID: > >> < > >> *CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com* > > > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> Unfortunately, I won't be able to do video if its being recorded, too > high > >> risk of something written on a wall ending up on video. > >> > >> John > >> > >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < > >> > > *antoine at sabot-durand.net* > wrote: > >> > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be recorder > >> for > >> > further reference. Hence the meeting will take place on redhat > Bluejeans > >> > meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and I'll > >> add > >> > you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> > *http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html* > > >> > >> ------------------------------ > >> > >> Message: 2 > >> Date: Fri, 24 Jun 2016 09:06:16 +0200 > >> From: Martin Kouba <*mkouba at redhat.com* > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: "John D. Ament" <*john.d.ament at gmail.com* >, > Antoine Sabot-Durand > >> <*antoine at sabot-durand.net* >, > cdi-dev <*cdi-dev at lists.jboss.org* > > >> Message-ID: <*576CDBE8.1040506 at redhat.com* > <576CDBE8.1040506 at redhat.com>> > >> Content-Type: text/plain; charset=windows-1252; format=flowed > > > > > >> > >> I should admit that it was my idea because I will not be able to attend > >> the meeting and would really like to see/hear the discussion and > >> arguments. > >> > >> Also I belive the recording should only be available to CDI EG memebers. > >> > >> Martin > >> > >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > Unfortunately, I won't be able to do video if its being recorded, too > >> > high risk of something written on a wall ending up on video. > >> > > >> > John > >> > > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > <*antoine at sabot-durand.net* *antoine at sabot-durand.net* >> wrote: > >> > > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be > >> > recorder for further reference. Hence the meeting will take place > on > >> > redhat Bluejeans meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and > >> > I'll add you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > cdi-dev mailing list > >> > *cdi-dev at lists.jboss.org* *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. > >> > > >> > > >> > > >> > _______________________________________________ > >> > 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. > >> > > >> > >> -- > >> Martin Kouba > >> Software Engineer > >> Red Hat, Czech Republic > >> > >> > >> ------------------------------ > >> > >> Message: 3 > >> Date: Fri, 24 Jun 2016 08:33:06 +0000 > >> From: Antoine Sabot-Durand <*antoine at sabot-durand.net* > > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Martin Kouba <*mkouba at redhat.com* >, "John D. > Ament" > >> <*john.d.ament at gmail.com* >, > cdi-dev <*cdi-dev at lists.jboss.org* > > >> Message-ID: > >> < > >> *CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com* > > > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> It will have restricted access and will be destroyed with the merge of > >> CDI-30 ;) > >> > >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba <*mkouba at redhat.com* > > a ?crit : > > > > > >> > >> > I should admit that it was my idea because I will not be able to > attend > >> > the meeting and would really like to see/hear the discussion and > >> arguments. > >> > > >> > Also I belive the recording should only be available to CDI EG > memebers. > >> > > >> > Martin > >> > > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > > Unfortunately, I won't be able to do video if its being recorded, > too > >> > > high risk of something written on a wall ending up on video. > >> > > > >> > > John > >> > > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > > <*antoine at sabot-durand.net* *antoine at sabot-durand.net* >> wrote: > >> > > > >> > > Hi all, > >> > > > >> > > As all of us won't be able to attend the meeting, it will be > >> > > recorder for further reference. Hence the meeting will take > place > >> on > >> > > redhat Bluejeans meeting service. > >> > > II've just added the url to the invitation. > >> > > If you want to attend and are not on the list please tell me and > >> > > I'll add you. > >> > > > >> > > Antoine > >> > > _______________________________________________ > >> > > cdi-dev mailing list > >> > > *cdi-dev at lists.jboss.org* *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. > >> > > > >> > > > >> > > > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > >> > -- > >> > Martin Kouba > >> > Software Engineer > >> > Red Hat, Czech Republic > >> > > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> > *http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html* > > >> > >> ------------------------------ > >> > >> Message: 4 > >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) > >> From: Michael Remijan <*mjremijan at yahoo.com* > > >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) > >> To: Antoine Sabot-Durand <*antoine at sabot-durand.net* > >, "John D. Ament" > >> <*john.d.ament at gmail.com* >, cdi-dev < > *cdi-dev at lists.jboss.org* > > >> Message-ID: > >> < > *2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com* > <2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com>> > >> Content-Type: text/plain; charset="utf-8" > >> > >> Is a build available yet to test the new Bootstrap? I'd like to upgrade > >> from 3.0.0.Alpha15 > >> > >> > >> > >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < > >> *antoine at sabot-durand.net* > wrote: > >> > >> > >> Error corrected. You can review the PR > >> Thx John > >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < > >> *antoine at sabot-durand.net* > a ?crit?: > >> > >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. > Let > >> me correct this > >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament <*john.d.ament at gmail.com* > > a > >> ?crit?: > >> > >> Antoine, > >> Did you go a little too deep in renaming container -> bootstrap? Looks > >> like many references to an EE container were changed.? Intentional? > >> John > > > > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < > >> *antoine at sabot-durand.net* > wrote: > >> > >> Hi all, > >> > > After integration of feedback, the new bootstrap API is in its final > >> form.Please review it carefully to find the possible last errors [1]. > >> Generated spec doc can also be read here [2] > >> Thanks for your help to integrate this very expected feature. > >> > >> Antoine > >> > >> > >> [1] *https://github.com/cdi-spec/cdi/pull/290* > > >> [2] > >> > *https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se* > > > > > > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> > *http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html* > > >> > >> ------------------------------ > > > > > >> > >> _______________________________________________ > >> 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. > >> > >> End of cdi-dev Digest, Vol 67, Issue 18 > >> *************************************** > >> > > > > _______________________________________________ > > 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. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > *http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html* > > > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 20 > *************************************** > > _______________________________________________ > 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. > _______________________________________________ > 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. > > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/0122326a/attachment-0001.html From EMIJIANG at uk.ibm.com Fri Jun 24 12:32:44 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Fri, 24 Jun 2016 17:32:44 +0100 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: Message-ID: hmmm. strange... why wasn't my request approved? I'm still on Requesting to join the video call. 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: "John D. Ament" To: Emily Jiang/UK/IBM at IBMGB, Antoine Sabot-Durand , Cc: Werner Keil , cdi-dev Date: 24/06/2016 17:22 Subject: Re: [cdi-dev] Tomorrow's meeting recording Sent by: cdi-dev-bounces at lists.jboss.org Yes it is. On Fri, Jun 24, 2016 at 12:02 PM Emily Jiang wrote: Is the meeting on? I'm on requesting to join the video call... nothing happened 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: "John D. Ament" To: Werner Keil , cdi-dev < cdi-dev at lists.jboss.org>, Date: 24/06/2016 14:29 Subject: Re: [cdi-dev] Tomorrow's meeting recording Sent by: cdi-dev-bounces at lists.jboss.org On Fri, Jun 24, 2016 at 9:19 AM Werner Keil wrote: Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not the only participant or EG sometimes lacking transparency. I would not even be able to join the hangout here at the client's office simply because there's no working audio HW in our laptops, not so much because of what's on the walls behind me (generally they are also extremely secretive, but there is nothing behind my desk that would unveil secrets;-) We have white board walls instead of rolling boards, so there's always something written on a wall somewhere. Here's an example: https://s-media-cache-ak0.pinimg.com/236x/77/41/0d/77410de3f8040c5edf6e613e10e11e93.jpg John Werner On Fri, Jun 24, 2016 at 3:14 PM, wrote: Send cdi-dev mailing list submissions to cdi-dev at lists.jboss.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.jboss.org/mailman/listinfo/cdi-dev or, via email, send a message with subject or body 'help' to cdi-dev-request at lists.jboss.org You can reach the person managing the list at cdi-dev-owner at lists.jboss.org When replying, please edit your Subject line so it is more specific than "Re: Contents of cdi-dev digest..." Today's Topics: 1. Re: Tomorrow's meeting recording (John D. Ament) ---------------------------------------------------------------------- Message: 1 Date: Fri, 24 Jun 2016 13:14:09 +0000 From: "John D. Ament" Subject: Re: [cdi-dev] Tomorrow's meeting recording To: Werner Keil , cdi-dev Message-ID: Content-Type: text/plain; charset="utf-8" On Fri, Jun 24, 2016 at 9:02 AM Werner Keil wrote: > >...too high > >risk of something written on a wall ending up on video. > > So much for transparency;-| > Werner, are you concerned that my employer is not being transparent about internal R&D items to outside parties? > > Werner > > > On Fri, Jun 24, 2016 at 2:59 PM, wrote: > >> Send cdi-dev mailing list submissions to >> cdi-dev at lists.jboss.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.jboss.org/mailman/listinfo/cdi-dev >> or, via email, send a message with subject or body 'help' to >> cdi-dev-request at lists.jboss.org >> >> You can reach the person managing the list at >> cdi-dev-owner at lists.jboss.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of cdi-dev digest..." >> >> >> Today's Topics: >> >> 1. Re: Tomorrow's meeting recording (John D. Ament) >> 2. Re: Tomorrow's meeting recording (Martin Kouba) >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 23 Jun 2016 23:24:43 +0000 >> From: "John D. Ament" >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: Antoine Sabot-Durand , cdi-dev >> >> Message-ID: >> < >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" > > >> >> Unfortunately, I won't be able to do video if its being recorded, too high >> risk of something written on a wall ending up on video. >> >> John >> >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < >> > antoine at sabot-durand.net> wrote: >> >> > Hi all, >> > >> > As all of us won't be able to attend the meeting, it will be recorder >> for >> > further reference. Hence the meeting will take place on redhat Bluejeans >> > meeting service. >> > II've just added the url to the invitation. >> > If you want to attend and are not on the list please tell me and I'll >> add >> > you. >> > >> > Antoine >> > _______________________________________________ >> > 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. >> > -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html >> >> ------------------------------ >> >> Message: 2 >> Date: Fri, 24 Jun 2016 09:06:16 +0200 >> From: Martin Kouba >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: "John D. Ament" , Antoine Sabot-Durand >> , cdi-dev < cdi-dev at lists.jboss.org> >> Message-ID: <576CDBE8.1040506 at redhat.com> >> Content-Type: text/plain; charset=windows-1252; format=flowed > > >> >> I should admit that it was my idea because I will not be able to attend >> the meeting and would really like to see/hear the discussion and >> arguments. >> >> Also I belive the recording should only be available to CDI EG memebers. >> >> Martin >> >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): >> > Unfortunately, I won't be able to do video if its being recorded, too >> > high risk of something written on a wall ending up on video. >> > >> > John >> > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand >> > > wrote: >> > >> > Hi all, >> > >> > As all of us won't be able to attend the meeting, it will be >> > recorder for further reference. Hence the meeting will take place on >> > redhat Bluejeans meeting service. >> > II've just added the url to the invitation. >> > If you want to attend and are not on the list please tell me and >> > I'll add you. >> > >> > Antoine >> > _______________________________________________ >> > 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. >> > >> > >> > >> > _______________________________________________ >> > 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. >> > >> >> -- >> Martin Kouba >> Software Engineer >> Red Hat, Czech Republic >> >> >> ------------------------------ >> >> Message: 3 >> Date: Fri, 24 Jun 2016 08:33:06 +0000 >> From: Antoine Sabot-Durand >> Subject: Re: [cdi-dev] Tomorrow's meeting recording >> To: Martin Kouba , "John D. Ament" >> , cdi-dev < cdi-dev at lists.jboss.org> >> Message-ID: >> < >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" > > >> >> It will have restricted access and will be destroyed with the merge of >> CDI-30 ;) >> >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba a ?crit : > > >> >> > I should admit that it was my idea because I will not be able to attend >> > the meeting and would really like to see/hear the discussion and >> arguments. >> > >> > Also I belive the recording should only be available to CDI EG memebers. >> > >> > Martin >> > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): >> > > Unfortunately, I won't be able to do video if its being recorded, too >> > > high risk of something written on a wall ending up on video. >> > > >> > > John >> > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand >> > > > wrote: >> > > >> > > Hi all, >> > > >> > > As all of us won't be able to attend the meeting, it will be >> > > recorder for further reference. Hence the meeting will take place >> on >> > > redhat Bluejeans meeting service. >> > > II've just added the url to the invitation. >> > > If you want to attend and are not on the list please tell me and >> > > I'll add you. >> > > >> > > Antoine >> > > _______________________________________________ >> > > 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. >> > > >> > > >> > > >> > > _______________________________________________ >> > > 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. >> > > >> > >> > -- >> > Martin Kouba >> > Software Engineer >> > Red Hat, Czech Republic >> > >> > -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html >> >> ------------------------------ >> >> Message: 4 >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) >> From: Michael Remijan >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) >> To: Antoine Sabot-Durand , "John D. Ament" >> , cdi-dev >> Message-ID: >> <2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com> >> Content-Type: text/plain; charset="utf-8" >> >> Is a build available yet to test the new Bootstrap? I'd like to upgrade >> from 3.0.0.Alpha15 >> >> >> >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < >> antoine at sabot-durand.net> wrote: >> >> >> Error corrected. You can review the PR >> Thx John >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < >> antoine at sabot-durand.net> a ?crit?: >> >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let >> me correct this >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament a >> ?crit?: >> >> Antoine, >> Did you go a little too deep in renaming container -> bootstrap? Looks >> like many references to an EE container were changed.? Intentional? >> John > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < >> antoine at sabot-durand.net> wrote: >> >> Hi all, >> > After integration of feedback, the new bootstrap API is in its final >> form.Please review it carefully to find the possible last errors [1]. >> Generated spec doc can also be read here [2] >> Thanks for your help to integrate this very expected feature. >> >> Antoine >> >> >> [1] https://github.com/cdi-spec/cdi/pull/290 >> [2] >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > >> >> >> _______________________________________________ >> 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. >> >> >> >> _______________________________________________ >> 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. >> >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html >> >> ------------------------------ > > >> >> _______________________________________________ >> 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. >> >> End of cdi-dev Digest, Vol 67, Issue 18 >> *************************************** >> > > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html ------------------------------ _______________________________________________ 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. End of cdi-dev Digest, Vol 67, Issue 20 *************************************** _______________________________________________ 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. _______________________________________________ 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. 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 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/f83394fa/attachment-0001.html From manovotn at redhat.com Fri Jun 24 12:58:23 2016 From: manovotn at redhat.com (Matej Novotny) Date: Fri, 24 Jun 2016 12:58:23 -0400 (EDT) Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: Message-ID: <897220994.1116267.1466787503473.JavaMail.zimbra@redhat.com> That is weird, nobody else had any problems with connection. Have you joined the BlueJeans call and not the Hangouts one? Matej ----- Original Message ----- > From: "Emily Jiang" > To: "John D. Ament" > Cc: "Werner Keil" , "cdi-dev" > Sent: Friday, June 24, 2016 6:32:44 PM > Subject: Re: [cdi-dev] Tomorrow's meeting recording > > hmmm. strange... why wasn't my request approved? I'm still on Requesting to > join the video call. > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: "John D. Ament" > To: Emily Jiang/UK/IBM at IBMGB, Antoine Sabot-Durand > , > Cc: Werner Keil , cdi-dev > Date: 24/06/2016 17:22 > Subject: Re: [cdi-dev] Tomorrow's meeting recording > Sent by: cdi-dev-bounces at lists.jboss.org > > > > > Yes it is. > > On Fri, Jun 24, 2016 at 12:02 PM Emily Jiang < EMIJIANG at uk.ibm.com > wrote: > Is the meeting on? I'm on requesting to join the video call... nothing > happened > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: "John D. Ament" < john.d.ament at gmail.com > > To: Werner Keil < werner.keil at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > >, > Date: 24/06/2016 14:29 > Subject: Re: [cdi-dev] Tomorrow's meeting recording > Sent by: cdi-dev-bounces at lists.jboss.org > > > > > > > On Fri, Jun 24, 2016 at 9:19 AM Werner Keil < werner.keil at gmail.com > wrote: > Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not the > only participant or EG sometimes lacking transparency. I would not even be > able to join the hangout here at the client's office simply because there's > no working audio HW in our laptops, not so much because of what's on the > walls behind me (generally they are also extremely secretive, but there is > nothing behind my desk that would unveil secrets;-) > > > We have white board walls instead of rolling boards, so there's always > something written on a wall somewhere. > > Here's an example: > https://s-media-cache-ak0.pinimg.com/236x/77/41/0d/77410de3f8040c5edf6e613e10e11e93.jpg > > John > > > Werner > > > On Fri, Jun 24, 2016 at 3:14 PM, < cdi-dev-request at lists.jboss.org > wrote: > Send cdi-dev mailing list submissions to > cdi-dev at lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request at lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner at lists.jboss.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. Re: Tomorrow's meeting recording (John D. Ament) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 24 Jun 2016 13:14:09 +0000 > > From: "John D. Ament" < john.d.ament at gmail.com > > Subject: Re: [cdi-dev] Tomorrow's meeting recording > To: Werner Keil < werner.keil at gmail.com >, cdi-dev > < cdi-dev at lists.jboss.org > > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > > On Fri, Jun 24, 2016 at 9:02 AM Werner Keil < werner.keil at gmail.com > wrote: > > > >...too high > > >risk of something written on a wall ending up on video. > > > > So much for transparency;-| > > > > Werner, are you concerned that my employer is not being transparent about > internal R&D items to outside parties? > > > > > > Werner > > > > > > On Fri, Jun 24, 2016 at 2:59 PM, < cdi-dev-request at lists.jboss.org > wrote: > > > >> Send cdi-dev mailing list submissions to > >> cdi-dev at lists.jboss.org > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> https://lists.jboss.org/mailman/listinfo/cdi-dev > >> or, via email, send a message with subject or body 'help' to > >> cdi-dev-request at lists.jboss.org > >> > >> You can reach the person managing the list at > >> cdi-dev-owner at lists.jboss.org > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of cdi-dev digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: Tomorrow's meeting recording (John D. Ament) > >> 2. Re: Tomorrow's meeting recording (Martin Kouba) > >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) > >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) > >> > >> > >> ---------------------------------------------------------------------- > >> > >> Message: 1 > >> Date: Thu, 23 Jun 2016 23:24:43 +0000 > >> From: "John D. Ament" < john.d.ament at gmail.com > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Antoine Sabot-Durand < antoine at sabot-durand.net >, cdi-dev > >> < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < > >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com > > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> Unfortunately, I won't be able to do video if its being recorded, too high > >> risk of something written on a wall ending up on video. > >> > >> John > >> > >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < > >> > > antoine at sabot-durand.net > wrote: > >> > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be recorder > >> for > >> > further reference. Hence the meeting will take place on redhat Bluejeans > >> > meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and I'll > >> add > >> > you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html > >> > >> ------------------------------ > >> > >> Message: 2 > >> Date: Fri, 24 Jun 2016 09:06:16 +0200 > >> From: Martin Kouba < mkouba at redhat.com > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: "John D. Ament" < john.d.ament at gmail.com >, Antoine Sabot-Durand > >> < antoine at sabot-durand.net >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: < 576CDBE8.1040506 at redhat.com > > >> Content-Type: text/plain; charset=windows-1252; format=flowed > > > > > >> > >> I should admit that it was my idea because I will not be able to attend > >> the meeting and would really like to see/hear the discussion and > >> arguments. > >> > >> Also I belive the recording should only be available to CDI EG memebers. > >> > >> Martin > >> > >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > Unfortunately, I won't be able to do video if its being recorded, too > >> > high risk of something written on a wall ending up on video. > >> > > >> > John > >> > > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > < antoine at sabot-durand.net > wrote: > >> > > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be > >> > recorder for further reference. Hence the meeting will take place on > >> > redhat Bluejeans meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and > >> > I'll add you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > >> > > >> > > >> > _______________________________________________ > >> > 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. > >> > > >> > >> -- > >> Martin Kouba > >> Software Engineer > >> Red Hat, Czech Republic > >> > >> > >> ------------------------------ > >> > >> Message: 3 > >> Date: Fri, 24 Jun 2016 08:33:06 +0000 > >> From: Antoine Sabot-Durand < antoine at sabot-durand.net > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Martin Kouba < mkouba at redhat.com >, "John D. Ament" > >> < john.d.ament at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < > >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com > > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> It will have restricted access and will be destroyed with the merge of > >> CDI-30 ;) > >> > >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba < mkouba at redhat.com > a ?crit : > > > > > >> > >> > I should admit that it was my idea because I will not be able to attend > >> > the meeting and would really like to see/hear the discussion and > >> arguments. > >> > > >> > Also I belive the recording should only be available to CDI EG memebers. > >> > > >> > Martin > >> > > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > > Unfortunately, I won't be able to do video if its being recorded, too > >> > > high risk of something written on a wall ending up on video. > >> > > > >> > > John > >> > > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > > < antoine at sabot-durand.net > wrote: > >> > > > >> > > Hi all, > >> > > > >> > > As all of us won't be able to attend the meeting, it will be > >> > > recorder for further reference. Hence the meeting will take place > >> on > >> > > redhat Bluejeans meeting service. > >> > > II've just added the url to the invitation. > >> > > If you want to attend and are not on the list please tell me and > >> > > I'll add you. > >> > > > >> > > Antoine > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > > >> > > > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > >> > -- > >> > Martin Kouba > >> > Software Engineer > >> > Red Hat, Czech Republic > >> > > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html > >> > >> ------------------------------ > >> > >> Message: 4 > >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) > >> From: Michael Remijan < mjremijan at yahoo.com > > >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) > >> To: Antoine Sabot-Durand < antoine at sabot-durand.net >, "John D. Ament" > >> < john.d.ament at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < 2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com > > >> Content-Type: text/plain; charset="utf-8" > >> > >> Is a build available yet to test the new Bootstrap? I'd like to upgrade > >> from 3.0.0.Alpha15 > >> > >> > >> > >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < > >> antoine at sabot-durand.net > wrote: > >> > >> > >> Error corrected. You can review the PR > >> Thx John > >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < > >> antoine at sabot-durand.net > a ?crit?: > >> > >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let > >> me correct this > >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament < john.d.ament at gmail.com > a > >> ?crit?: > >> > >> Antoine, > >> Did you go a little too deep in renaming container -> bootstrap? Looks > >> like many references to an EE container were changed.? Intentional? > >> John > > > > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < > >> antoine at sabot-durand.net > wrote: > >> > >> Hi all, > >> > > After integration of feedback, the new bootstrap API is in its final > >> form.Please review it carefully to find the possible last errors [1]. > >> Generated spec doc can also be read here [2] > >> Thanks for your help to integrate this very expected feature. > >> > >> Antoine > >> > >> > >> [1] https://github.com/cdi-spec/cdi/pull/290 > >> [2] > >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > > > > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html > >> > >> ------------------------------ > > > > > >> > >> _______________________________________________ > >> 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. > >> > >> End of cdi-dev Digest, Vol 67, Issue 18 > >> *************************************** > >> > > > > _______________________________________________ > > 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. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html > > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 20 > *************************************** > > _______________________________________________ > 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. > _______________________________________________ > 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. > > > 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 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. > > 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 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. From antoine at sabot-durand.net Fri Jun 24 16:06:56 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Fri, 24 Jun 2016 20:06:56 +0000 Subject: [cdi-dev] CDI-30 F2F meeting summary Message-ID: Hi all, Just to sum up the meeting we had today about CDI-30 and John's PR. If I forgot something, the attendee (John, Matej and Werner) can of course correct or add content. While we agreed that this feature is very important, it's obvious that each of us has a different way of seeing it. To try to get out of the current dead end, the idea was to split the problem in 2 goal : 1. Provide low level SPI for framework and spec developers to reuse cdi built in scope. Roughly it consist of giving the possibility to activate and deactivate context programmatically. If it's possible this should be done without adding new interface to keep the SPI as simple as possible 2. Provide a mean for standard (yet advanced) developers to activate/deactivate built-in contexts at will (probably thru interceptors) Goal 1 is mandatory for EDR2 while goal 2 is a nice to have. John start the work on goal 1 in the coming days. For goal 2 it would be nice that each of us think about one or more real life use case that this context activation could allow to check if the design SPI fits the need. Antoine -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/8ed2e4f0/attachment.html From EMIJIANG at uk.ibm.com Fri Jun 24 16:48:53 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Fri, 24 Jun 2016 21:48:53 +0100 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: <897220994.1116267.1466787503473.JavaMail.zimbra@redhat.com> References: <897220994.1116267.1466787503473.JavaMail.zimbra@redhat.com> Message-ID: I clicked on the calendar invitation sent by Antoine, which is hangout. Very odd... 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: Matej Novotny To: Emily Jiang/UK/IBM at IBMGB, Cc: "John D. Ament" , Werner Keil , cdi-dev Date: 24/06/2016 17:58 Subject: Re: [cdi-dev] Tomorrow's meeting recording That is weird, nobody else had any problems with connection. Have you joined the BlueJeans call and not the Hangouts one? Matej ----- Original Message ----- > From: "Emily Jiang" > To: "John D. Ament" > Cc: "Werner Keil" , "cdi-dev" > Sent: Friday, June 24, 2016 6:32:44 PM > Subject: Re: [cdi-dev] Tomorrow's meeting recording > > hmmm. strange... why wasn't my request approved? I'm still on Requesting to > join the video call. > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: "John D. Ament" > To: Emily Jiang/UK/IBM at IBMGB, Antoine Sabot-Durand > , > Cc: Werner Keil , cdi-dev > Date: 24/06/2016 17:22 > Subject: Re: [cdi-dev] Tomorrow's meeting recording > Sent by: cdi-dev-bounces at lists.jboss.org > > > > > Yes it is. > > On Fri, Jun 24, 2016 at 12:02 PM Emily Jiang < EMIJIANG at uk.ibm.com > wrote: > Is the meeting on? I'm on requesting to join the video call... nothing > happened > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: "John D. Ament" < john.d.ament at gmail.com > > To: Werner Keil < werner.keil at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > >, > Date: 24/06/2016 14:29 > Subject: Re: [cdi-dev] Tomorrow's meeting recording > Sent by: cdi-dev-bounces at lists.jboss.org > > > > > > > On Fri, Jun 24, 2016 at 9:19 AM Werner Keil < werner.keil at gmail.com > wrote: > Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not the > only participant or EG sometimes lacking transparency. I would not even be > able to join the hangout here at the client's office simply because there's > no working audio HW in our laptops, not so much because of what's on the > walls behind me (generally they are also extremely secretive, but there is > nothing behind my desk that would unveil secrets;-) > > > We have white board walls instead of rolling boards, so there's always > something written on a wall somewhere. > > Here's an example: > https://s-media-cache-ak0.pinimg.com/236x/77/41/0d/77410de3f8040c5edf6e613e10e11e93.jpg > > John > > > Werner > > > On Fri, Jun 24, 2016 at 3:14 PM, < cdi-dev-request at lists.jboss.org > wrote: > Send cdi-dev mailing list submissions to > cdi-dev at lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request at lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner at lists.jboss.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. Re: Tomorrow's meeting recording (John D. Ament) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 24 Jun 2016 13:14:09 +0000 > > From: "John D. Ament" < john.d.ament at gmail.com > > Subject: Re: [cdi-dev] Tomorrow's meeting recording > To: Werner Keil < werner.keil at gmail.com >, cdi-dev > < cdi-dev at lists.jboss.org > > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > > On Fri, Jun 24, 2016 at 9:02 AM Werner Keil < werner.keil at gmail.com > wrote: > > > >...too high > > >risk of something written on a wall ending up on video. > > > > So much for transparency;-| > > > > Werner, are you concerned that my employer is not being transparent about > internal R&D items to outside parties? > > > > > > Werner > > > > > > On Fri, Jun 24, 2016 at 2:59 PM, < cdi-dev-request at lists.jboss.org > wrote: > > > >> Send cdi-dev mailing list submissions to > >> cdi-dev at lists.jboss.org > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> https://lists.jboss.org/mailman/listinfo/cdi-dev > >> or, via email, send a message with subject or body 'help' to > >> cdi-dev-request at lists.jboss.org > >> > >> You can reach the person managing the list at > >> cdi-dev-owner at lists.jboss.org > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of cdi-dev digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: Tomorrow's meeting recording (John D. Ament) > >> 2. Re: Tomorrow's meeting recording (Martin Kouba) > >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) > >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) > >> > >> > >> ---------------------------------------------------------------------- > >> > >> Message: 1 > >> Date: Thu, 23 Jun 2016 23:24:43 +0000 > >> From: "John D. Ament" < john.d.ament at gmail.com > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Antoine Sabot-Durand < antoine at sabot-durand.net >, cdi-dev > >> < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < > >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com > > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> Unfortunately, I won't be able to do video if its being recorded, too high > >> risk of something written on a wall ending up on video. > >> > >> John > >> > >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < > >> > > antoine at sabot-durand.net > wrote: > >> > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be recorder > >> for > >> > further reference. Hence the meeting will take place on redhat Bluejeans > >> > meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and I'll > >> add > >> > you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html > >> > >> ------------------------------ > >> > >> Message: 2 > >> Date: Fri, 24 Jun 2016 09:06:16 +0200 > >> From: Martin Kouba < mkouba at redhat.com > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: "John D. Ament" < john.d.ament at gmail.com >, Antoine Sabot-Durand > >> < antoine at sabot-durand.net >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: < 576CDBE8.1040506 at redhat.com > > >> Content-Type: text/plain; charset=windows-1252; format=flowed > > > > > >> > >> I should admit that it was my idea because I will not be able to attend > >> the meeting and would really like to see/hear the discussion and > >> arguments. > >> > >> Also I belive the recording should only be available to CDI EG memebers. > >> > >> Martin > >> > >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > Unfortunately, I won't be able to do video if its being recorded, too > >> > high risk of something written on a wall ending up on video. > >> > > >> > John > >> > > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > < antoine at sabot-durand.net > wrote: > >> > > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be > >> > recorder for further reference. Hence the meeting will take place on > >> > redhat Bluejeans meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and > >> > I'll add you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > >> > > >> > > >> > _______________________________________________ > >> > 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. > >> > > >> > >> -- > >> Martin Kouba > >> Software Engineer > >> Red Hat, Czech Republic > >> > >> > >> ------------------------------ > >> > >> Message: 3 > >> Date: Fri, 24 Jun 2016 08:33:06 +0000 > >> From: Antoine Sabot-Durand < antoine at sabot-durand.net > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Martin Kouba < mkouba at redhat.com >, "John D. Ament" > >> < john.d.ament at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < > >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com > > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> It will have restricted access and will be destroyed with the merge of > >> CDI-30 ;) > >> > >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba < mkouba at redhat.com > a ?crit : > > > > > >> > >> > I should admit that it was my idea because I will not be able to attend > >> > the meeting and would really like to see/hear the discussion and > >> arguments. > >> > > >> > Also I belive the recording should only be available to CDI EG memebers. > >> > > >> > Martin > >> > > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > > Unfortunately, I won't be able to do video if its being recorded, too > >> > > high risk of something written on a wall ending up on video. > >> > > > >> > > John > >> > > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > > < antoine at sabot-durand.net > wrote: > >> > > > >> > > Hi all, > >> > > > >> > > As all of us won't be able to attend the meeting, it will be > >> > > recorder for further reference. Hence the meeting will take place > >> on > >> > > redhat Bluejeans meeting service. > >> > > II've just added the url to the invitation. > >> > > If you want to attend and are not on the list please tell me and > >> > > I'll add you. > >> > > > >> > > Antoine > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > > >> > > > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > >> > -- > >> > Martin Kouba > >> > Software Engineer > >> > Red Hat, Czech Republic > >> > > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html > >> > >> ------------------------------ > >> > >> Message: 4 > >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) > >> From: Michael Remijan < mjremijan at yahoo.com > > >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) > >> To: Antoine Sabot-Durand < antoine at sabot-durand.net >, "John D. Ament" > >> < john.d.ament at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < 2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com > > >> Content-Type: text/plain; charset="utf-8" > >> > >> Is a build available yet to test the new Bootstrap? I'd like to upgrade > >> from 3.0.0.Alpha15 > >> > >> > >> > >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < > >> antoine at sabot-durand.net > wrote: > >> > >> > >> Error corrected. You can review the PR > >> Thx John > >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < > >> antoine at sabot-durand.net > a ?crit?: > >> > >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let > >> me correct this > >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament < john.d.ament at gmail.com > a > >> ?crit?: > >> > >> Antoine, > >> Did you go a little too deep in renaming container -> bootstrap? Looks > >> like many references to an EE container were changed.? Intentional? > >> John > > > > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < > >> antoine at sabot-durand.net > wrote: > >> > >> Hi all, > >> > > After integration of feedback, the new bootstrap API is in its final > >> form.Please review it carefully to find the possible last errors [1]. > >> Generated spec doc can also be read here [2] > >> Thanks for your help to integrate this very expected feature. > >> > >> Antoine > >> > >> > >> [1] https://github.com/cdi-spec/cdi/pull/290 > >> [2] > >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > > > > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html > >> > >> ------------------------------ > > > > > >> > >> _______________________________________________ > >> 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. > >> > >> End of cdi-dev Digest, Vol 67, Issue 18 > >> *************************************** > >> > > > > _______________________________________________ > > 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. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html > > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 20 > *************************************** > > _______________________________________________ > 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. > _______________________________________________ > 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. > > > 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 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. > > 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 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/f934f998/attachment-0001.html From john.d.ament at gmail.com Fri Jun 24 16:55:52 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Fri, 24 Jun 2016 20:55:52 +0000 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: <897220994.1116267.1466787503473.JavaMail.zimbra@redhat.com> Message-ID: A second invite was sent, replacing the hangout link with a bluejeans link. John On Fri, Jun 24, 2016 at 4:49 PM Emily Jiang wrote: > I clicked on the calendar invitation sent by Antoine, which is hangout > . > Very odd... > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: Matej Novotny > To: Emily Jiang/UK/IBM at IBMGB, > Cc: "John D. Ament" , Werner Keil < > werner.keil at gmail.com>, cdi-dev > Date: 24/06/2016 17:58 > Subject: Re: [cdi-dev] Tomorrow's meeting recording > > > > That is weird, nobody else had any problems with connection. > Have you joined the BlueJeans call and not the Hangouts one? > > Matej > > ----- Original Message ----- > > From: "Emily Jiang" > > To: "John D. Ament" > > Cc: "Werner Keil" , "cdi-dev" < > cdi-dev at lists.jboss.org> > > Sent: Friday, June 24, 2016 6:32:44 PM > > Subject: Re: [cdi-dev] Tomorrow's meeting recording > > > > hmmm. strange... why wasn't my request approved? I'm still on Requesting > to > > join the video call. > > > > 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 at uk.ibm.com > > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > > > > > > From: "John D. Ament" > > To: Emily Jiang/UK/IBM at IBMGB, Antoine Sabot-Durand > > , > > Cc: Werner Keil , cdi-dev < > cdi-dev at lists.jboss.org> > > Date: 24/06/2016 17:22 > > Subject: Re: [cdi-dev] Tomorrow's meeting recording > > Sent by: cdi-dev-bounces at lists.jboss.org > > > > > > > > > > Yes it is. > > > > On Fri, Jun 24, 2016 at 12:02 PM Emily Jiang < EMIJIANG at uk.ibm.com > > wrote: > > Is the meeting on? I'm on requesting to join the video call... nothing > > happened > > > > 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 at uk.ibm.com > > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > > > > > > From: "John D. Ament" < john.d.ament at gmail.com > > > To: Werner Keil < werner.keil at gmail.com >, cdi-dev < > cdi-dev at lists.jboss.org > > >, > > Date: 24/06/2016 14:29 > > Subject: Re: [cdi-dev] Tomorrow's meeting recording > > Sent by: cdi-dev-bounces at lists.jboss.org > > > > > > > > > > > > > > On Fri, Jun 24, 2016 at 9:19 AM Werner Keil < werner.keil at gmail.com > > wrote: > > Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not > the > > only participant or EG sometimes lacking transparency. I would not even > be > > able to join the hangout here at the client's office simply because > there's > > no working audio HW in our laptops, not so much because of what's on the > > walls behind me (generally they are also extremely secretive, but there > is > > nothing behind my desk that would unveil secrets;-) > > > > > > We have white board walls instead of rolling boards, so there's always > > something written on a wall somewhere. > > > > Here's an example: > > > https://s-media-cache-ak0.pinimg.com/236x/77/41/0d/77410de3f8040c5edf6e613e10e11e93.jpg > > > > John > > > > > > Werner > > > > > > On Fri, Jun 24, 2016 at 3:14 PM, < cdi-dev-request at lists.jboss.org > > wrote: > > Send cdi-dev mailing list submissions to > > cdi-dev at lists.jboss.org > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://lists.jboss.org/mailman/listinfo/cdi-dev > > or, via email, send a message with subject or body 'help' to > > cdi-dev-request at lists.jboss.org > > > > You can reach the person managing the list at > > cdi-dev-owner at lists.jboss.org > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of cdi-dev digest..." > > > > > > Today's Topics: > > > > 1. Re: Tomorrow's meeting recording (John D. Ament) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 24 Jun 2016 13:14:09 +0000 > > > > From: "John D. Ament" < john.d.ament at gmail.com > > > Subject: Re: [cdi-dev] Tomorrow's meeting recording > > To: Werner Keil < werner.keil at gmail.com >, cdi-dev > > < cdi-dev at lists.jboss.org > > > Message-ID: > > > > Content-Type: text/plain; charset="utf-8" > > > > > > On Fri, Jun 24, 2016 at 9:02 AM Werner Keil < werner.keil at gmail.com > > wrote: > > > > > >...too high > > > >risk of something written on a wall ending up on video. > > > > > > So much for transparency;-| > > > > > > > Werner, are you concerned that my employer is not being transparent about > > internal R&D items to outside parties? > > > > > > > > > > Werner > > > > > > > > > On Fri, Jun 24, 2016 at 2:59 PM, < cdi-dev-request at lists.jboss.org > > wrote: > > > > > >> Send cdi-dev mailing list submissions to > > >> cdi-dev at lists.jboss.org > > >> > > >> To subscribe or unsubscribe via the World Wide Web, visit > > >> https://lists.jboss.org/mailman/listinfo/cdi-dev > > >> or, via email, send a message with subject or body 'help' to > > >> cdi-dev-request at lists.jboss.org > > >> > > >> You can reach the person managing the list at > > >> cdi-dev-owner at lists.jboss.org > > >> > > >> When replying, please edit your Subject line so it is more specific > > >> than "Re: Contents of cdi-dev digest..." > > >> > > >> > > >> Today's Topics: > > >> > > >> 1. Re: Tomorrow's meeting recording (John D. Ament) > > >> 2. Re: Tomorrow's meeting recording (Martin Kouba) > > >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) > > >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) > > >> > > >> > > >> ---------------------------------------------------------------------- > > >> > > >> Message: 1 > > >> Date: Thu, 23 Jun 2016 23:24:43 +0000 > > >> From: "John D. Ament" < john.d.ament at gmail.com > > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > > >> To: Antoine Sabot-Durand < antoine at sabot-durand.net >, cdi-dev > > >> < cdi-dev at lists.jboss.org > > > >> Message-ID: > > >> < > > >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com > > > >> Content-Type: text/plain; charset="utf-8" > > > > > > > > >> > > >> Unfortunately, I won't be able to do video if its being recorded, too > high > > >> risk of something written on a wall ending up on video. > > >> > > >> John > > >> > > >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < > > >> > > > antoine at sabot-durand.net > wrote: > > >> > > >> > Hi all, > > >> > > > >> > As all of us won't be able to attend the meeting, it will be > recorder > > >> for > > >> > further reference. Hence the meeting will take place on redhat > Bluejeans > > >> > meeting service. > > >> > II've just added the url to the invitation. > > >> > If you want to attend and are not on the list please tell me and > I'll > > >> add > > >> > you. > > >> > > > >> > Antoine > > >> > _______________________________________________ > > >> > 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. > > >> > > > -------------- next part -------------- > > >> An HTML attachment was scrubbed... > > >> URL: > > >> > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html > > >> > > >> ------------------------------ > > >> > > >> Message: 2 > > >> Date: Fri, 24 Jun 2016 09:06:16 +0200 > > >> From: Martin Kouba < mkouba at redhat.com > > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > > >> To: "John D. Ament" < john.d.ament at gmail.com >, Antoine Sabot-Durand > > >> < antoine at sabot-durand.net >, cdi-dev < cdi-dev at lists.jboss.org > > > >> Message-ID: < 576CDBE8.1040506 at redhat.com > > > >> Content-Type: text/plain; charset=windows-1252; format=flowed > > > > > > > > >> > > >> I should admit that it was my idea because I will not be able to > attend > > >> the meeting and would really like to see/hear the discussion and > > >> arguments. > > >> > > >> Also I belive the recording should only be available to CDI EG > memebers. > > >> > > >> Martin > > >> > > >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > > >> > Unfortunately, I won't be able to do video if its being recorded, > too > > >> > high risk of something written on a wall ending up on video. > > >> > > > >> > John > > >> > > > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > > >> > < antoine at sabot-durand.net > > wrote: > > >> > > > >> > Hi all, > > >> > > > >> > As all of us won't be able to attend the meeting, it will be > > >> > recorder for further reference. Hence the meeting will take place on > > >> > redhat Bluejeans meeting service. > > >> > II've just added the url to the invitation. > > >> > If you want to attend and are not on the list please tell me and > > >> > I'll add you. > > >> > > > >> > Antoine > > >> > _______________________________________________ > > >> > 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. > > >> > > > >> > > > >> > > > >> > _______________________________________________ > > >> > 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. > > >> > > > >> > > >> -- > > >> Martin Kouba > > >> Software Engineer > > >> Red Hat, Czech Republic > > >> > > >> > > >> ------------------------------ > > >> > > >> Message: 3 > > >> Date: Fri, 24 Jun 2016 08:33:06 +0000 > > >> From: Antoine Sabot-Durand < antoine at sabot-durand.net > > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > > >> To: Martin Kouba < mkouba at redhat.com >, "John D. Ament" > > >> < john.d.ament at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > > > >> Message-ID: > > >> < > > >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com > > > >> Content-Type: text/plain; charset="utf-8" > > > > > > > > >> > > >> It will have restricted access and will be destroyed with the merge of > > >> CDI-30 ;) > > >> > > >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba < mkouba at redhat.com > a > ?crit : > > > > > > > > >> > > >> > I should admit that it was my idea because I will not be able to > attend > > >> > the meeting and would really like to see/hear the discussion and > > >> arguments. > > >> > > > >> > Also I belive the recording should only be available to CDI EG > memebers. > > >> > > > >> > Martin > > >> > > > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > > >> > > Unfortunately, I won't be able to do video if its being recorded, > too > > >> > > high risk of something written on a wall ending up on video. > > >> > > > > >> > > John > > >> > > > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > > >> > > < antoine at sabot-durand.net > > wrote: > > >> > > > > >> > > Hi all, > > >> > > > > >> > > As all of us won't be able to attend the meeting, it will be > > >> > > recorder for further reference. Hence the meeting will take place > > >> on > > >> > > redhat Bluejeans meeting service. > > >> > > II've just added the url to the invitation. > > >> > > If you want to attend and are not on the list please tell me and > > >> > > I'll add you. > > >> > > > > >> > > Antoine > > >> > > _______________________________________________ > > >> > > 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. > > >> > > > > >> > > > > >> > > > > >> > > _______________________________________________ > > >> > > 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. > > >> > > > > >> > > > >> > -- > > >> > Martin Kouba > > >> > Software Engineer > > >> > Red Hat, Czech Republic > > >> > > > >> > > > -------------- next part -------------- > > >> An HTML attachment was scrubbed... > > >> URL: > > >> > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html > > >> > > >> ------------------------------ > > >> > > >> Message: 4 > > >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) > > >> From: Michael Remijan < mjremijan at yahoo.com > > > >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) > > >> To: Antoine Sabot-Durand < antoine at sabot-durand.net >, "John D. > Ament" > > >> < john.d.ament at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > > > >> Message-ID: > > >> < 2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com > > > >> Content-Type: text/plain; charset="utf-8" > > >> > > >> Is a build available yet to test the new Bootstrap? I'd like to > upgrade > > >> from 3.0.0.Alpha15 > > >> > > >> > > >> > > >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < > > >> antoine at sabot-durand.net > wrote: > > >> > > >> > > >> Error corrected. You can review the PR > > >> Thx John > > >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < > > >> antoine at sabot-durand.net > a ?crit?: > > >> > > >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. > Let > > >> me correct this > > >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament < john.d.ament at gmail.com > > a > > >> ?crit?: > > >> > > >> Antoine, > > >> Did you go a little too deep in renaming container -> bootstrap? Looks > > >> like many references to an EE container were changed.? Intentional? > > >> John > > > > > > > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < > > >> antoine at sabot-durand.net > wrote: > > >> > > >> Hi all, > > >> > > > After integration of feedback, the new bootstrap API is in its final > > >> form.Please review it carefully to find the possible last errors [1]. > > >> Generated spec doc can also be read here [2] > > >> Thanks for your help to integrate this very expected feature. > > >> > > >> Antoine > > >> > > >> > > >> [1] https://github.com/cdi-spec/cdi/pull/290 > > >> [2] > > >> > https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > > > > > > > >> > > >> > > >> _______________________________________________ > > >> 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. > > >> > > >> > > >> > > >> _______________________________________________ > > >> 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. > > >> > > >> > > >> -------------- next part -------------- > > >> An HTML attachment was scrubbed... > > >> URL: > > >> > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html > > >> > > >> ------------------------------ > > > > > > > > >> > > >> _______________________________________________ > > >> 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. > > >> > > >> End of cdi-dev Digest, Vol 67, Issue 18 > > >> *************************************** > > >> > > > > > > _______________________________________________ > > > 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. > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > > > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html > > > > > > ------------------------------ > > > > _______________________________________________ > > 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. > > > > End of cdi-dev Digest, Vol 67, Issue 20 > > *************************************** > > > > _______________________________________________ > > 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. > > _______________________________________________ > > 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. > > > > > > 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 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. > > > > 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 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. > > > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/de9ec791/attachment-0001.html From issues at jboss.org Fri Jun 24 17:27:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 17:27:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-618) I can associate an existing context to another thread In-Reply-To: References: Message-ID: John Ament created CDI-618: ------------------------------ Summary: I can associate an existing context to another thread Key: CDI-618 URL: https://issues.jboss.org/browse/CDI-618 Project: CDI Specification Issues Issue Type: Feature Request Components: Contexts Affects Versions: 2.0-EDR1 Reporter: John Ament As a framework developer, when I start a new thread, or associate a new task to an existing thread, I can temporarily associate a context associated with another thread with the new thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 17:28:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 17:28:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-619) Simple for developers approach to starting contexts In-Reply-To: References: Message-ID: John Ament created CDI-619: ------------------------------ Summary: Simple for developers approach to starting contexts Key: CDI-619 URL: https://issues.jboss.org/browse/CDI-619 Project: CDI Specification Issues Issue Type: Feature Request Components: Contexts Affects Versions: 2.0-EDR1 Reporter: John Ament As an application developer, I can leverage a cross-functional feature in CDI to start a context for the duration of an invocation. This should be safe enough that if this given context is already active, it does not get reactivated. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From john.d.ament at gmail.com Fri Jun 24 17:28:09 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Fri, 24 Jun 2016 21:28:09 +0000 Subject: [cdi-dev] CDI-30 - Creating a managed context Message-ID: All, One of the discussion points from today was around where activation belongs. I pushed up a branch with a rough example of what this might look like https://github.com/johnament/cdi/commit/f4cb91dca0eeb7edef5d4238f55ca413a0711e26 One of my concerns with doing this is that to get a context object from the bean manager, it needs to be active. This is in the javadocs: Obtains an active {@linkplain javax.enterprise.context.spi.Context context object} for the given. If we change this, it risks breaking compatibility. Let me know your thoughts. John -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/50b09a26/attachment.html From john.d.ament at gmail.com Fri Jun 24 17:35:25 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Fri, 24 Jun 2016 21:35:25 +0000 Subject: [cdi-dev] CDI-30 F2F meeting summary In-Reply-To: References: Message-ID: One of the follow up items was to split CDI-30 into multiple tickets, to keep focus on just the portions we're working on. I've created the following follow up tickets: https://issues.jboss.org/browse/CDI-618 https://issues.jboss.org/browse/CDI-619 While I also realize that https://issues.jboss.org/browse/CDI-452 is critical for this discussion, and may be somewhat related to both of these tickets. My goal is to tackle all of these for EDR2, and will hopefully in coming days. John On Fri, Jun 24, 2016 at 4:08 PM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: > Hi all, > > Just to sum up the meeting we had today about CDI-30 and John's PR. > If I forgot something, the attendee (John, Matej and Werner) can of course > correct or add content. > > While we agreed that this feature is very important, it's obvious that > each of us has a different way of seeing it. > To try to get out of the current dead end, the idea was to split the > problem in 2 goal : > > 1. Provide low level SPI for framework and spec developers to reuse cdi > built in scope. Roughly it consist of giving the possibility to activate > and deactivate context programmatically. If it's possible this should be > done without adding new interface to keep the SPI as simple as possible > > 2. Provide a mean for standard (yet advanced) developers to > activate/deactivate built-in contexts at will (probably thru interceptors) > > Goal 1 is mandatory for EDR2 while goal 2 is a nice to have. > John start the work on goal 1 in the coming days. > > For goal 2 it would be nice that each of us think about one or more real > life use case that this context activation could allow to check if the > design SPI fits the need. > > Antoine > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/606b6e64/attachment.html From issues at jboss.org Fri Jun 24 17:41:01 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 17:41:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-452) Specify that web scoped (request, session, application) beans are injectable in async servlets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257048#comment-13257048 ] John Ament commented on CDI-452: -------------------------------- [~edburns] I just want to confirm. Your expectation here is that you can bridge the existing request context/session context from the servlet request in to the new async thread, allowing the same instances of the beans (and in turn, their data) to be accessed in both threads. If so, what synchronization would you expect, if any, to be provided by the CDI container? Or would you prefer to leave it to the developer to handle synchronization concerns? > Specify that web scoped (request, session, application) beans are injectable in async servlets > ---------------------------------------------------------------------------------------------- > > Key: CDI-452 > URL: https://issues.jboss.org/browse/CDI-452 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Ed Burns > Priority: Trivial > Fix For: 2.0 (discussion) > > > Consider this code based on this blog post: < https://weblogs.java.net/blog/swchan2/archive/2013/06/06/asynchronous-servlet-and-java-ee-concurrency-utilities >. > {code} > @WebServlet(urlPatterns="/test2", asyncSupported=true) > public class TestAsyncMESServlet extends HttpServlet { > @Resource > private ManagedExecutorService managedExecutorService; > @Inject > MyRunnableImpl myRunnableImpl; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse res) > throws ServletException, IOException { > final AsyncContext asyncContext = req.startAsync(); > final PrintWriter writer = res.getWriter(); > managedExecutorService.submit(myRunnableImpl); > } > public static class MyRunnableImpl implements Runnable { > @Inject > Bean bean; // Bean is @RequestScoped > @Override > public void run() { > writer.println("Done"); > asyncContext.complete(); > } > } > } > {code} > According to Jozef Hartzinger, this currently does not work, because only @Dependent and @ApplicationScoped beans are propagated to the new thread. To keep CDI relevant in light of the reactive programming movement and the popularity of node.js, we need to make this work. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 17:41:01 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 17:41:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-452) Specify that web scoped (request, session, application) beans are injectable in async servlets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament reassigned CDI-452: ------------------------------ Assignee: John Ament > Specify that web scoped (request, session, application) beans are injectable in async servlets > ---------------------------------------------------------------------------------------------- > > Key: CDI-452 > URL: https://issues.jboss.org/browse/CDI-452 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Ed Burns > Assignee: John Ament > Priority: Trivial > Fix For: 2.0 (discussion) > > > Consider this code based on this blog post: < https://weblogs.java.net/blog/swchan2/archive/2013/06/06/asynchronous-servlet-and-java-ee-concurrency-utilities >. > {code} > @WebServlet(urlPatterns="/test2", asyncSupported=true) > public class TestAsyncMESServlet extends HttpServlet { > @Resource > private ManagedExecutorService managedExecutorService; > @Inject > MyRunnableImpl myRunnableImpl; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse res) > throws ServletException, IOException { > final AsyncContext asyncContext = req.startAsync(); > final PrintWriter writer = res.getWriter(); > managedExecutorService.submit(myRunnableImpl); > } > public static class MyRunnableImpl implements Runnable { > @Inject > Bean bean; // Bean is @RequestScoped > @Override > public void run() { > writer.println("Done"); > asyncContext.complete(); > } > } > } > {code} > According to Jozef Hartzinger, this currently does not work, because only @Dependent and @ApplicationScoped beans are propagated to the new thread. To keep CDI relevant in light of the reactive programming movement and the popularity of node.js, we need to make this work. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 17:41:02 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 17:41:02 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-452) Specify that web scoped (request, session, application) beans are injectable in async servlets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament updated CDI-452: --------------------------- Component/s: Contexts > Specify that web scoped (request, session, application) beans are injectable in async servlets > ---------------------------------------------------------------------------------------------- > > Key: CDI-452 > URL: https://issues.jboss.org/browse/CDI-452 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts, Java EE integration > Affects Versions: 1.0 > Reporter: Ed Burns > Assignee: John Ament > Priority: Trivial > Fix For: 2.0 (discussion) > > > Consider this code based on this blog post: < https://weblogs.java.net/blog/swchan2/archive/2013/06/06/asynchronous-servlet-and-java-ee-concurrency-utilities >. > {code} > @WebServlet(urlPatterns="/test2", asyncSupported=true) > public class TestAsyncMESServlet extends HttpServlet { > @Resource > private ManagedExecutorService managedExecutorService; > @Inject > MyRunnableImpl myRunnableImpl; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse res) > throws ServletException, IOException { > final AsyncContext asyncContext = req.startAsync(); > final PrintWriter writer = res.getWriter(); > managedExecutorService.submit(myRunnableImpl); > } > public static class MyRunnableImpl implements Runnable { > @Inject > Bean bean; // Bean is @RequestScoped > @Override > public void run() { > writer.println("Done"); > asyncContext.complete(); > } > } > } > {code} > According to Jozef Hartzinger, this currently does not work, because only @Dependent and @ApplicationScoped beans are propagated to the new thread. To keep CDI relevant in light of the reactive programming movement and the popularity of node.js, we need to make this work. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 17:41:03 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 17:41:03 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-619) Simple for developers approach to starting contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CDI-619 started by John Ament. -------------------------------------- > Simple for developers approach to starting contexts > --------------------------------------------------- > > Key: CDI-619 > URL: https://issues.jboss.org/browse/CDI-619 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 2.0-EDR1 > Reporter: John Ament > Assignee: John Ament > > As an application developer, I can leverage a cross-functional feature in CDI to start a context for the duration of an invocation. > This should be safe enough that if this given context is already active, it does not get reactivated. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 17:41:02 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 17:41:02 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-452) Specify that web scoped (request, session, application) beans are injectable in async servlets In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament updated CDI-452: --------------------------- Priority: Major (was: Trivial) > Specify that web scoped (request, session, application) beans are injectable in async servlets > ---------------------------------------------------------------------------------------------- > > Key: CDI-452 > URL: https://issues.jboss.org/browse/CDI-452 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts, Java EE integration > Affects Versions: 1.0 > Reporter: Ed Burns > Assignee: John Ament > Fix For: 2.0 (discussion) > > > Consider this code based on this blog post: < https://weblogs.java.net/blog/swchan2/archive/2013/06/06/asynchronous-servlet-and-java-ee-concurrency-utilities >. > {code} > @WebServlet(urlPatterns="/test2", asyncSupported=true) > public class TestAsyncMESServlet extends HttpServlet { > @Resource > private ManagedExecutorService managedExecutorService; > @Inject > MyRunnableImpl myRunnableImpl; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse res) > throws ServletException, IOException { > final AsyncContext asyncContext = req.startAsync(); > final PrintWriter writer = res.getWriter(); > managedExecutorService.submit(myRunnableImpl); > } > public static class MyRunnableImpl implements Runnable { > @Inject > Bean bean; // Bean is @RequestScoped > @Override > public void run() { > writer.println("Done"); > asyncContext.complete(); > } > } > } > {code} > According to Jozef Hartzinger, this currently does not work, because only @Dependent and @ApplicationScoped beans are propagated to the new thread. To keep CDI relevant in light of the reactive programming movement and the popularity of node.js, we need to make this work. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 17:42:00 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 17:42:00 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-619) Simple for developers approach to starting contexts In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CDI-619 stopped by John Ament. -------------------------------------- > Simple for developers approach to starting contexts > --------------------------------------------------- > > Key: CDI-619 > URL: https://issues.jboss.org/browse/CDI-619 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 2.0-EDR1 > Reporter: John Ament > Assignee: John Ament > > As an application developer, I can leverage a cross-functional feature in CDI to start a context for the duration of an invocation. > This should be safe enough that if this given context is already active, it does not get reactivated. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 18:27:01 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 18:27:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-30) An API for managing built in contexts designed for other frameworks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament updated CDI-30: -------------------------- Summary: An API for managing built in contexts designed for other frameworks (was: An API for managing built in contexts) > An API for managing built in contexts designed for other frameworks > ------------------------------------------------------------------- > > Key: CDI-30 > URL: https://issues.jboss.org/browse/CDI-30 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 1.0 > Reporter: Nicklas Karlsson > Assignee: John Ament > Fix For: 2.0 (discussion) > > > Add management API for built in contexts allowing them to be reused as needed. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From issues at jboss.org Fri Jun 24 18:33:01 2016 From: issues at jboss.org (John Ament (JIRA)) Date: Fri, 24 Jun 2016 18:33:01 -0400 (EDT) Subject: [cdi-dev] [JBoss JIRA] (CDI-30) An API for managing built in contexts designed for other frameworks In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/CDI-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Ament updated CDI-30: -------------------------- Description: In order to allow CDI to play well in the general ecosystem, it needs to have SPIs. These SPIs need to allow other libraries to do things like register beans (CDI extensions), look up a bean manager, and get managed versions of its classes. CDI has no way currently to support a framework starting and stopping built in contexts. These built in contexts are not really clear in how they are started, other than the container is responsible for starting them. This means its near impossible for an external library which is not Java EE aware to start these built in contexts. Being able to reuse these contexts allow developers to build their beans once and reuse them in many use cases. These use cases may include: 1. Quartz Scheduler/CDI Integration. A Prototype of this is available in DeltaSpike, where jobs can be managed beans, by overriding the InstanceJobFactory, and can have contexts started via an annotation. To bring it a step further, Quartz, in order to mirror Java EE capabilities, may want to say that during the execution of a job, an instance of a request context is active. To do this, the developer should not need to do anything, but instead Quartz may automatically register a job listener that starts and stops the context (see: http://www.quartz-scheduler.org/documentation/quartz-2.2.x/cookbook/JobListeners.html) 2. Camel-CDI. Camel may want to say that during the execution of a route, a request context is active. 3. Netty/CDI (or any arbitrary network based server). During the reception of a message over TCP, a request is active. Likewise, for the entire TCP connection a session context is active. 4. Sparkjava/CDI. Assuming that sparkjava isn't running in a servlet container, during the execution of an arbitrary reactive method call, a request context is available for use. was:Add management API for built in contexts allowing them to be reused as needed. > An API for managing built in contexts designed for other frameworks > ------------------------------------------------------------------- > > Key: CDI-30 > URL: https://issues.jboss.org/browse/CDI-30 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 1.0 > Reporter: Nicklas Karlsson > Assignee: John Ament > Fix For: 2.0 (discussion) > > > In order to allow CDI to play well in the general ecosystem, it needs to have SPIs. These SPIs need to allow other libraries to do things like register beans (CDI extensions), look up a bean manager, and get managed versions of its classes. > CDI has no way currently to support a framework starting and stopping built in contexts. These built in contexts are not really clear in how they are started, other than the container is responsible for starting them. This means its near impossible for an external library which is not Java EE aware to start these built in contexts. Being able to reuse these contexts allow developers to build their beans once and reuse them in many use cases. > These use cases may include: > 1. Quartz Scheduler/CDI Integration. A Prototype of this is available in DeltaSpike, where jobs can be managed beans, by overriding the InstanceJobFactory, and can have contexts started via an annotation. To bring it a step further, Quartz, in order to mirror Java EE capabilities, may want to say that during the execution of a job, an instance of a request context is active. To do this, the developer should not need to do anything, but instead Quartz may automatically register a job listener that starts and stops the context (see: http://www.quartz-scheduler.org/documentation/quartz-2.2.x/cookbook/JobListeners.html) > 2. Camel-CDI. Camel may want to say that during the execution of a route, a request context is active. > 3. Netty/CDI (or any arbitrary network based server). During the reception of a message over TCP, a request is active. Likewise, for the entire TCP connection a session context is active. > 4. Sparkjava/CDI. Assuming that sparkjava isn't running in a servlet container, during the execution of an arbitrary reactive method call, a request context is available for use. -- This message was sent by Atlassian JIRA (v6.4.11#64026) From john.d.ament at gmail.com Sat Jun 25 10:10:46 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Sat, 25 Jun 2016 14:10:46 +0000 Subject: [cdi-dev] CDI-30 - Creating a managed context In-Reply-To: References: Message-ID: All, I have the flip side of this change available as well. https://github.com/johnament/cdi/blob/6fbd7d834e11295a3a4490294cde0ad18bee6b33/api/src/test/java/org/jboss/cdi/api/test/ContextManagementExample.java In this version, activation is done directly from BeanManager instead of the secondary context object. I'm also thinking with this commit that ManagedContext should actually be "UnmanagedContext" to clarify that its not being handled in the container. John PS - One of the use cases I put in the JIRA ticket was around quartz integration. This is what the resulting integration looks like public class CDIJobListener implements JobListener { public static final String CONTEXT_NAME = "CDIJobListener.cdi_context"; @Override public String getName() { return "cdi"; } @Override public void jobToBeExecuted(JobExecutionContext jobExecutionContext) { BeanManager beanManager = CDI.current().getBeanManager(); ManagedContext requestContext = beanManager.activateContext(RequestScoped.class); jobExecutionContext.getMergedJobDataMap().put(CONTEXT_NAME, requestContext); } @Override public void jobExecutionVetoed(JobExecutionContext jobExecutionContext) { ManagedContext managedContext = (ManagedContext)jobExecutionContext.getMergedJobDataMap().get(CONTEXT_NAME); managedContext.deactivate(); } @Override public void jobWasExecuted(JobExecutionContext jobExecutionContext, JobExecutionException e) { jobExecutionVetoed(jobExecutionContext); } } On Fri, Jun 24, 2016 at 5:28 PM John D. Ament wrote: > All, > > One of the discussion points from today was around where activation > belongs. I pushed up a branch with a rough example of what this might look > like > > > https://github.com/johnament/cdi/commit/f4cb91dca0eeb7edef5d4238f55ca413a0711e26 > > One of my concerns with doing this is that to get a context object from > the bean manager, it needs to be active. This is in the javadocs: Obtains > an active {@linkplain javax.enterprise.context.spi.Context context object} > for the given. If we change this, it risks breaking compatibility. > > Let me know your thoughts. > > John > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160625/6b53a9b2/attachment.html From john.d.ament at gmail.com Tue Jun 28 22:36:52 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Wed, 29 Jun 2016 02:36:52 +0000 Subject: [cdi-dev] New PR for CDI-30 Message-ID: All, I've raised a new PR for the changes around CDI-30, based on Friday and today's discussions. I've gone with the approach that BeanManager provides a lookup for unmanaged contexts, and those unmanaged contexts can be started/stopped in a manual way. https://github.com/cdi-spec/cdi/pull/296 I haven't updated the spec yet, and the javadocs are pretty barebones. I would greatly appreciate input on what to add. John -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/1956c58f/attachment-0001.html From EMIJIANG at uk.ibm.com Wed Jun 29 04:43:44 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Wed, 29 Jun 2016 08:43:44 +0000 Subject: [cdi-dev] Tomorrow's meeting recording In-Reply-To: References: <897220994.1116267.1466787503473.JavaMail.zimbra@redhat.com> Message-ID: ah. I did not get the 2nd bluejeans link, which explains the mistery. thanks John! 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: "John D. Ament" To: Emily Jiang/UK/IBM at IBMGB, Matej Novotny , Cc: Werner Keil , cdi-dev Date: 24/06/2016 21:57 Subject: Re: [cdi-dev] Tomorrow's meeting recording Sent by: cdi-dev-bounces at lists.jboss.org A second invite was sent, replacing the hangout link with a bluejeans link. John On Fri, Jun 24, 2016 at 4:49 PM Emily Jiang wrote: I clicked on the calendar invitation sent by Antoine, which is hangout. Very odd... 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: Matej Novotny To: Emily Jiang/UK/IBM at IBMGB, Cc: "John D. Ament" , Werner Keil < werner.keil at gmail.com>, cdi-dev Date: 24/06/2016 17:58 Subject: Re: [cdi-dev] Tomorrow's meeting recording That is weird, nobody else had any problems with connection. Have you joined the BlueJeans call and not the Hangouts one? Matej ----- Original Message ----- > From: "Emily Jiang" > To: "John D. Ament" > Cc: "Werner Keil" , "cdi-dev" < cdi-dev at lists.jboss.org> > Sent: Friday, June 24, 2016 6:32:44 PM > Subject: Re: [cdi-dev] Tomorrow's meeting recording > > hmmm. strange... why wasn't my request approved? I'm still on Requesting to > join the video call. > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: "John D. Ament" > To: Emily Jiang/UK/IBM at IBMGB, Antoine Sabot-Durand > , > Cc: Werner Keil , cdi-dev < cdi-dev at lists.jboss.org> > Date: 24/06/2016 17:22 > Subject: Re: [cdi-dev] Tomorrow's meeting recording > Sent by: cdi-dev-bounces at lists.jboss.org > > > > > Yes it is. > > On Fri, Jun 24, 2016 at 12:02 PM Emily Jiang < EMIJIANG at uk.ibm.com > wrote: > Is the meeting on? I'm on requesting to join the video call... nothing > happened > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: "John D. Ament" < john.d.ament at gmail.com > > To: Werner Keil < werner.keil at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > >, > Date: 24/06/2016 14:29 > Subject: Re: [cdi-dev] Tomorrow's meeting recording > Sent by: cdi-dev-bounces at lists.jboss.org > > > > > > > On Fri, Jun 24, 2016 at 9:19 AM Werner Keil < werner.keil at gmail.com > wrote: > Well just with my "Java EE Guardians" hat on, I'm saying, Oracle is not the > only participant or EG sometimes lacking transparency. I would not even be > able to join the hangout here at the client's office simply because there's > no working audio HW in our laptops, not so much because of what's on the > walls behind me (generally they are also extremely secretive, but there is > nothing behind my desk that would unveil secrets;-) > > > We have white board walls instead of rolling boards, so there's always > something written on a wall somewhere. > > Here's an example: > https://s-media-cache-ak0.pinimg.com/236x/77/41/0d/77410de3f8040c5edf6e613e10e11e93.jpg > > John > > > Werner > > > On Fri, Jun 24, 2016 at 3:14 PM, < cdi-dev-request at lists.jboss.org > wrote: > Send cdi-dev mailing list submissions to > cdi-dev at lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request at lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner at lists.jboss.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. Re: Tomorrow's meeting recording (John D. Ament) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 24 Jun 2016 13:14:09 +0000 > > From: "John D. Ament" < john.d.ament at gmail.com > > Subject: Re: [cdi-dev] Tomorrow's meeting recording > To: Werner Keil < werner.keil at gmail.com >, cdi-dev > < cdi-dev at lists.jboss.org > > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > > On Fri, Jun 24, 2016 at 9:02 AM Werner Keil < werner.keil at gmail.com > wrote: > > > >...too high > > >risk of something written on a wall ending up on video. > > > > So much for transparency;-| > > > > Werner, are you concerned that my employer is not being transparent about > internal R&D items to outside parties? > > > > > > Werner > > > > > > On Fri, Jun 24, 2016 at 2:59 PM, < cdi-dev-request at lists.jboss.org > wrote: > > > >> Send cdi-dev mailing list submissions to > >> cdi-dev at lists.jboss.org > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> https://lists.jboss.org/mailman/listinfo/cdi-dev > >> or, via email, send a message with subject or body 'help' to > >> cdi-dev-request at lists.jboss.org > >> > >> You can reach the person managing the list at > >> cdi-dev-owner at lists.jboss.org > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of cdi-dev digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: Tomorrow's meeting recording (John D. Ament) > >> 2. Re: Tomorrow's meeting recording (Martin Kouba) > >> 3. Re: Tomorrow's meeting recording (Antoine Sabot-Durand) > >> 4. Re: Please review PR 290 (bootstrap se) (Michael Remijan) > >> > >> > >> ---------------------------------------------------------------------- > >> > >> Message: 1 > >> Date: Thu, 23 Jun 2016 23:24:43 +0000 > >> From: "John D. Ament" < john.d.ament at gmail.com > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Antoine Sabot-Durand < antoine at sabot-durand.net >, cdi-dev > >> < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < > >> CAOqetn-DCJ17cvKxBuc_BM14gBxub3gMvRZKEhKovM3z06snMw at mail.gmail.com > > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> Unfortunately, I won't be able to do video if its being recorded, too high > >> risk of something written on a wall ending up on video. > >> > >> John > >> > >> On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand < > >> > > antoine at sabot-durand.net > wrote: > >> > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be recorder > >> for > >> > further reference. Hence the meeting will take place on redhat Bluejeans > >> > meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and I'll > >> add > >> > you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160623/57308212/attachment-0001.html > >> > >> ------------------------------ > >> > >> Message: 2 > >> Date: Fri, 24 Jun 2016 09:06:16 +0200 > >> From: Martin Kouba < mkouba at redhat.com > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: "John D. Ament" < john.d.ament at gmail.com >, Antoine Sabot-Durand > >> < antoine at sabot-durand.net >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: < 576CDBE8.1040506 at redhat.com > > >> Content-Type: text/plain; charset=windows-1252; format=flowed > > > > > >> > >> I should admit that it was my idea because I will not be able to attend > >> the meeting and would really like to see/hear the discussion and > >> arguments. > >> > >> Also I belive the recording should only be available to CDI EG memebers. > >> > >> Martin > >> > >> Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > Unfortunately, I won't be able to do video if its being recorded, too > >> > high risk of something written on a wall ending up on video. > >> > > >> > John > >> > > >> > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > < antoine at sabot-durand.net > wrote: > >> > > >> > Hi all, > >> > > >> > As all of us won't be able to attend the meeting, it will be > >> > recorder for further reference. Hence the meeting will take place on > >> > redhat Bluejeans meeting service. > >> > II've just added the url to the invitation. > >> > If you want to attend and are not on the list please tell me and > >> > I'll add you. > >> > > >> > Antoine > >> > _______________________________________________ > >> > 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. > >> > > >> > > >> > > >> > _______________________________________________ > >> > 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. > >> > > >> > >> -- > >> Martin Kouba > >> Software Engineer > >> Red Hat, Czech Republic > >> > >> > >> ------------------------------ > >> > >> Message: 3 > >> Date: Fri, 24 Jun 2016 08:33:06 +0000 > >> From: Antoine Sabot-Durand < antoine at sabot-durand.net > > >> Subject: Re: [cdi-dev] Tomorrow's meeting recording > >> To: Martin Kouba < mkouba at redhat.com >, "John D. Ament" > >> < john.d.ament at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < > >> CABu-YBTCfCkH6Xf7E0GgghK1agXDmq2sRK05LSeUV4pfpKkVVw at mail.gmail.com > > >> Content-Type: text/plain; charset="utf-8" > > > > > >> > >> It will have restricted access and will be destroyed with the merge of > >> CDI-30 ;) > >> > >> Le ven. 24 juin 2016 ? 09:06, Martin Kouba < mkouba at redhat.com > a ?crit : > > > > > >> > >> > I should admit that it was my idea because I will not be able to attend > >> > the meeting and would really like to see/hear the discussion and > >> arguments. > >> > > >> > Also I belive the recording should only be available to CDI EG memebers. > >> > > >> > Martin > >> > > >> > Dne 24.6.2016 v 01:24 John D. Ament napsal(a): > >> > > Unfortunately, I won't be able to do video if its being recorded, too > >> > > high risk of something written on a wall ending up on video. > >> > > > >> > > John > >> > > > >> > > On Thu, Jun 23, 2016 at 4:38 PM Antoine Sabot-Durand > >> > > < antoine at sabot-durand.net > wrote: > >> > > > >> > > Hi all, > >> > > > >> > > As all of us won't be able to attend the meeting, it will be > >> > > recorder for further reference. Hence the meeting will take place > >> on > >> > > redhat Bluejeans meeting service. > >> > > II've just added the url to the invitation. > >> > > If you want to attend and are not on the list please tell me and > >> > > I'll add you. > >> > > > >> > > Antoine > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > > >> > > > >> > > _______________________________________________ > >> > > 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. > >> > > > >> > > >> > -- > >> > Martin Kouba > >> > Software Engineer > >> > Red Hat, Czech Republic > >> > > >> > > -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/660a43b7/attachment-0001.html > >> > >> ------------------------------ > >> > >> Message: 4 > >> Date: Fri, 24 Jun 2016 12:58:07 +0000 (UTC) > >> From: Michael Remijan < mjremijan at yahoo.com > > >> Subject: Re: [cdi-dev] Please review PR 290 (bootstrap se) > >> To: Antoine Sabot-Durand < antoine at sabot-durand.net >, "John D. Ament" > >> < john.d.ament at gmail.com >, cdi-dev < cdi-dev at lists.jboss.org > > >> Message-ID: > >> < 2064584222.725169.1466773087613.JavaMail.yahoo at mail.yahoo.com > > >> Content-Type: text/plain; charset="utf-8" > >> > >> Is a build available yet to test the new Bootstrap? I'd like to upgrade > >> from 3.0.0.Alpha15 > >> > >> > >> > >> On Thursday, June 23, 2016 6:47 AM, Antoine Sabot-Durand < > >> antoine at sabot-durand.net > wrote: > >> > >> > >> Error corrected. You can review the PR > >> Thx John > >> Le?jeu. 23 juin 2016 ??13:06, Antoine Sabot-Durand < > >> antoine at sabot-durand.net > a ?crit?: > >> > >> OMG you're right. Javadoc has suffered from renaming refactoring :-(. Let > >> me correct this > >> Le?jeu. 23 juin 2016 ??12:09, John D. Ament < john.d.ament at gmail.com > a > >> ?crit?: > >> > >> Antoine, > >> Did you go a little too deep in renaming container -> bootstrap? Looks > >> like many references to an EE container were changed.? Intentional? > >> John > > > > > >> On Thu, Jun 23, 2016 at 6:06 AM Antoine Sabot-Durand < > >> antoine at sabot-durand.net > wrote: > >> > >> Hi all, > >> > > After integration of feedback, the new bootstrap API is in its final > >> form.Please review it carefully to find the possible last errors [1]. > >> Generated spec doc can also be read here [2] > >> Thanks for your help to integrate this very expected feature. > >> > >> Antoine > >> > >> > >> [1] https://github.com/cdi-spec/cdi/pull/290 > >> [2] > >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > > > > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> > >> _______________________________________________ > >> 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. > >> > >> > >> -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: > >> http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d48fb094/attachment.html > >> > >> ------------------------------ > > > > > >> > >> _______________________________________________ > >> 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. > >> > >> End of cdi-dev Digest, Vol 67, Issue 18 > >> *************************************** > >> > > > > _______________________________________________ > > 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. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160624/d685f4c0/attachment.html > > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 20 > *************************************** > > _______________________________________________ > 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. > _______________________________________________ > 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. > > > 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 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. > > 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 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. 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 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/f88145e9/attachment-0001.html From EMIJIANG at uk.ibm.com Wed Jun 29 04:46:51 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Wed, 29 Jun 2016 09:46:51 +0100 Subject: [cdi-dev] the next CDI f2f meeting Message-ID: Hi Antoine, Have you decided on the dates of the CDI F2F in September? I need to plan my other activities around it. The earlier you can finalise the date the better. 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/d374816b/attachment.html From antoine at sabot-durand.net Wed Jun 29 04:50:12 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Wed, 29 Jun 2016 08:50:12 +0000 Subject: [cdi-dev] the next CDI f2f meeting In-Reply-To: References: Message-ID: You're right Emily. I try to close the Doodle this week. Antoine Le mer. 29 juin 2016 ? 10:46, Emily Jiang a ?crit : > Hi Antoine, > > Have you decided on the dates of the CDI F2F in September? I need to plan > my other activities around it. The earlier you can finalise the date the > better. > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/a2e80654/attachment.html From EMIJIANG at uk.ibm.com Wed Jun 29 04:54:15 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Wed, 29 Jun 2016 09:54:15 +0100 Subject: [cdi-dev] the next CDI f2f meeting In-Reply-To: References: Message-ID: thank you Antoine! 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: Antoine Sabot-Durand To: Emily Jiang/UK/IBM at IBMGB, Cc: cdi-dev at lists.jboss.org Date: 29/06/2016 09:50 Subject: Re: the next CDI f2f meeting You're right Emily. I try to close the Doodle this week. Antoine Le mer. 29 juin 2016 ? 10:46, Emily Jiang a ?crit : Hi Antoine, Have you decided on the dates of the CDI F2F in September? I need to plan my other activities around it. The earlier you can finalise the date the better. 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/88bdd798/attachment.html From antoine at sabot-durand.net Wed Jun 29 07:20:52 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Wed, 29 Jun 2016 11:20:52 +0000 Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) Message-ID: Hi all, I just push changed decided in yesterday meeting to PR 290[1]. Please review them and give a +1 on it if you're ok for the merge. Generated version of the spec is available here [2]. Antoine [1]: https://github.com/cdi-spec/cdi/pull/290 [2]: https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/af99dd90/attachment.html From john.d.ament at gmail.com Wed Jun 29 07:26:28 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Wed, 29 Jun 2016 11:26:28 +0000 Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) In-Reply-To: References: Message-ID: Antoine, Looks like we may have missed one of the earlier comments, about reusing the instance vs creating a new one each time. John On Wed, Jun 29, 2016 at 7:23 AM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: > Hi all, > > I just push changed decided in yesterday meeting to PR 290[1]. Please > review them and give a +1 on it if you're ok for the merge. > Generated version of the spec is available here [2]. > > Antoine > > [1]: https://github.com/cdi-spec/cdi/pull/290 > [2]: > https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > _______________________________________________ > 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/78cfc3a5/attachment-0001.html From antoine at sabot-durand.net Wed Jun 29 07:46:52 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Wed, 29 Jun 2016 11:46:52 +0000 Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) In-Reply-To: References: Message-ID: You mean the instance of SeContainerInitializer obtained thru getInstance() ? Le mer. 29 juin 2016 ? 13:26, John D. Ament a ?crit : > Antoine, > > Looks like we may have missed one of the earlier comments, about reusing > the instance vs creating a new one each time. > > John > > On Wed, Jun 29, 2016 at 7:23 AM Antoine Sabot-Durand < > antoine at sabot-durand.net> wrote: > >> Hi all, >> >> I just push changed decided in yesterday meeting to PR 290[1]. Please >> review them and give a +1 on it if you're ok for the merge. >> Generated version of the spec is available here [2]. >> >> Antoine >> >> [1]: https://github.com/cdi-spec/cdi/pull/290 >> [2]: >> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se >> >> _______________________________________________ >> 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. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/c4a2d278/attachment.html From werner.keil at gmail.com Wed Jun 29 08:39:18 2016 From: werner.keil at gmail.com (Werner Keil) Date: Wed, 29 Jun 2016 14:39:18 +0200 Subject: [cdi-dev] the next CDI f2f meeting Message-ID: Hi, With at least JavaOne taking 10+ days (I also should be at the EC F2F a few days before) September is pretty packed for me and I'm afraid I could not take another week day(s) off then. If part of it also had a video link similar to last week's call, I'd be happy to join like that if possible. Werner On Wed, Jun 29, 2016 at 1:26 PM, wrote: > Send cdi-dev mailing list submissions to > cdi-dev at lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request at lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner at lists.jboss.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. the next CDI f2f meeting (Emily Jiang) > 2. Re: the next CDI f2f meeting (Antoine Sabot-Durand) > 3. Re: the next CDI f2f meeting (Emily Jiang) > 4. Last review on PR 290 (SE bootstrap) (Antoine Sabot-Durand) > 5. Re: Last review on PR 290 (SE bootstrap) (John D. Ament) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 29 Jun 2016 09:46:51 +0100 > From: Emily Jiang > Subject: [cdi-dev] the next CDI f2f meeting > To: "Antoine Sabot-Durand" > Cc: cdi-dev at lists.jboss.org > Message-ID: > < > OF45017F7A.5D7A618E-ON80257FE1.00300BBE-80257FE1.0030409C at notes.na.collabserv.com > > > > Content-Type: text/plain; charset="us-ascii" > > Hi Antoine, > > Have you decided on the dates of the CDI F2F in September? I need to plan > my other activities around it. The earlier you can finalise the date the > better. > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/d374816b/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Wed, 29 Jun 2016 08:50:12 +0000 > From: Antoine Sabot-Durand > Subject: Re: [cdi-dev] the next CDI f2f meeting > To: Emily Jiang > Cc: cdi-dev at lists.jboss.org > Message-ID: > < > CABu-YBQ18C8rC38qDYHoSE6aYH8w+h906QBq8129z8imoqu0XQ at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > You're right Emily. I try to close the Doodle this week. > > Antoine > Le mer. 29 juin 2016 ? 10:46, Emily Jiang a ?crit : > > > Hi Antoine, > > > > Have you decided on the dates of the CDI F2F in September? I need to plan > > my other activities around it. The earlier you can finalise the date the > > better. > > > > 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 at uk.ibm.com > > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > 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 > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/a2e80654/attachment-0001.html > > ------------------------------ > > Message: 3 > Date: Wed, 29 Jun 2016 09:54:15 +0100 > From: Emily Jiang > Subject: Re: [cdi-dev] the next CDI f2f meeting > To: Antoine Sabot-Durand > Cc: cdi-dev at lists.jboss.org > Message-ID: > < > OFAFA70F86.9D0FD7A9-ON80257FE1.0030DC78-80257FE1.0030EE07 at notes.na.collabserv.com > > > > Content-Type: text/plain; charset="iso-8859-1" > > thank you Antoine! > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: Antoine Sabot-Durand > To: Emily Jiang/UK/IBM at IBMGB, > Cc: cdi-dev at lists.jboss.org > Date: 29/06/2016 09:50 > Subject: Re: the next CDI f2f meeting > > > > You're right Emily. I try to close the Doodle this week. > > Antoine > Le mer. 29 juin 2016 ? 10:46, Emily Jiang a ?crit : > Hi Antoine, > > Have you decided on the dates of the CDI F2F in September? I need to plan > my other activities around it. The earlier you can finalise the date the > better. > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > 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 > > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/88bdd798/attachment-0001.html > > ------------------------------ > > Message: 4 > Date: Wed, 29 Jun 2016 11:20:52 +0000 > From: Antoine Sabot-Durand > Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) > To: cdi-dev > Message-ID: > AY9g at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > I just push changed decided in yesterday meeting to PR 290[1]. Please > review them and give a +1 on it if you're ok for the merge. > Generated version of the spec is available here [2]. > > Antoine > > [1]: https://github.com/cdi-spec/cdi/pull/290 > [2]: > https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/af99dd90/attachment-0001.html > > ------------------------------ > > Message: 5 > Date: Wed, 29 Jun 2016 11:26:28 +0000 > From: "John D. Ament" > Subject: Re: [cdi-dev] Last review on PR 290 (SE bootstrap) > To: Antoine Sabot-Durand , cdi-dev > > Message-ID: > PGZpkv0YWYiQphmgAg at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Antoine, > > Looks like we may have missed one of the earlier comments, about reusing > the instance vs creating a new one each time. > > John > > On Wed, Jun 29, 2016 at 7:23 AM Antoine Sabot-Durand < > antoine at sabot-durand.net> wrote: > > > Hi all, > > > > I just push changed decided in yesterday meeting to PR 290[1]. Please > > review them and give a +1 on it if you're ok for the merge. > > Generated version of the spec is available here [2]. > > > > Antoine > > > > [1]: https://github.com/cdi-spec/cdi/pull/290 > > [2]: > > https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se > > > > _______________________________________________ > > 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. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/78cfc3a5/attachment.html > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 67, Issue 31 > *************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/433c88f8/attachment-0001.html From john.d.ament at gmail.com Wed Jun 29 09:07:36 2016 From: john.d.ament at gmail.com (John D. Ament) Date: Wed, 29 Jun 2016 09:07:36 -0400 Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) In-Reply-To: References: Message-ID: Yes. On Jun 29, 2016 7:47 AM, "Antoine Sabot-Durand" wrote: > You mean the instance of SeContainerInitializer obtained thru > getInstance() ? > Le mer. 29 juin 2016 ? 13:26, John D. Ament a > ?crit : > >> Antoine, >> >> Looks like we may have missed one of the earlier comments, about reusing >> the instance vs creating a new one each time. >> >> John >> >> On Wed, Jun 29, 2016 at 7:23 AM Antoine Sabot-Durand < >> antoine at sabot-durand.net> wrote: >> >>> Hi all, >>> >>> I just push changed decided in yesterday meeting to PR 290[1]. Please >>> review them and give a +1 on it if you're ok for the merge. >>> Generated version of the spec is available here [2]. >>> >>> Antoine >>> >>> [1]: https://github.com/cdi-spec/cdi/pull/290 >>> [2]: >>> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se >>> >>> _______________________________________________ >>> 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. >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/ce163e91/attachment.html From EMIJIANG at uk.ibm.com Wed Jun 29 09:40:31 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Wed, 29 Jun 2016 14:40:31 +0100 Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) In-Reply-To: References: Message-ID: Antoine, I think you did a global replacement on bootstrap. Scanning may also have negative impact on se performance. 'se performance' does not make sense. I would prefer not to change bootstrap to se in this sentence. It should still read Scanning may also have negative impact on bootstrap performance. 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: "John D. Ament" To: Antoine Sabot-Durand , Cc: cdi-dev Date: 29/06/2016 14:08 Subject: Re: [cdi-dev] Last review on PR 290 (SE bootstrap) Sent by: cdi-dev-bounces at lists.jboss.org Yes. On Jun 29, 2016 7:47 AM, "Antoine Sabot-Durand" wrote: You mean the instance of SeContainerInitializer obtained thru getInstance() ? Le mer. 29 juin 2016 ? 13:26, John D. Ament a ?crit : Antoine, Looks like we may have missed one of the earlier comments, about reusing the instance vs creating a new one each time. John On Wed, Jun 29, 2016 at 7:23 AM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: Hi all, I just push changed decided in yesterday meeting to PR 290[1]. Please review them and give a +1 on it if you're ok for the merge. Generated version of the spec is available here [2]. Antoine [1]: https://github.com/cdi-spec/cdi/pull/290 [2]: https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se _______________________________________________ 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. _______________________________________________ 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/69b3d748/attachment.html From EMIJIANG at uk.ibm.com Wed Jun 29 10:36:17 2016 From: EMIJIANG at uk.ibm.com (Emily Jiang) Date: Wed, 29 Jun 2016 15:36:17 +0100 Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) In-Reply-To: References: Message-ID: +1 on both. Great job! [1]: https://github.com/cdi-spec/cdi/pull/290 [2]: https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: Emily Jiang/UK/IBM at IBMGB To: "John D. Ament" , Cc: cdi-dev Date: 29/06/2016 14:42 Subject: Re: [cdi-dev] Last review on PR 290 (SE bootstrap) Sent by: cdi-dev-bounces at lists.jboss.org Antoine, I think you did a global replacement on bootstrap. Scanning may also have negative impact on se performance. 'se performance' does not make sense. I would prefer not to change bootstrap to se in this sentence. It should still read Scanning may also have negative impact on bootstrap performance. 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 at uk.ibm.com Lotus Notes: Emily Jiang/UK/IBM at IBMGB From: "John D. Ament" To: Antoine Sabot-Durand , Cc: cdi-dev Date: 29/06/2016 14:08 Subject: Re: [cdi-dev] Last review on PR 290 (SE bootstrap) Sent by: cdi-dev-bounces at lists.jboss.org Yes. On Jun 29, 2016 7:47 AM, "Antoine Sabot-Durand" wrote: You mean the instance of SeContainerInitializer obtained thru getInstance() ? Le mer. 29 juin 2016 ? 13:26, John D. Ament a ?crit : Antoine, Looks like we may have missed one of the earlier comments, about reusing the instance vs creating a new one each time. John On Wed, Jun 29, 2016 at 7:23 AM Antoine Sabot-Durand < antoine at sabot-durand.net> wrote: Hi all, I just push changed decided in yesterday meeting to PR 290[1]. Please review them and give a +1 on it if you're ok for the merge. Generated version of the spec is available here [2]. Antoine [1]: https://github.com/cdi-spec/cdi/pull/290 [2]: https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se _______________________________________________ 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. _______________________________________________ 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. 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 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. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/0ec4db77/attachment-0001.html From antoine at sabot-durand.net Wed Jun 29 11:04:55 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Wed, 29 Jun 2016 15:04:55 +0000 Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) In-Reply-To: References: Message-ID: Yes Emily. A bad search & replace during refactoring. Corrected Le mer. 29 juin 2016 ? 15:40, Emily Jiang a ?crit : > Antoine, > I think you did a global replacement on bootstrap. > > Scanning may also have negative impact on se performance. > 'se performance' does not make sense. I would prefer not to change > bootstrap to se in this sentence. > > It should still read > Scanning may also have negative impact on bootstrap performance. > > 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 at uk.ibm.com > Lotus Notes: Emily Jiang/UK/IBM at IBMGB > > > > > From: "John D. Ament" > To: Antoine Sabot-Durand , > Cc: cdi-dev > Date: 29/06/2016 14:08 > Subject: Re: [cdi-dev] Last review on PR 290 (SE bootstrap) > Sent by: cdi-dev-bounces at lists.jboss.org > ------------------------------ > > > > Yes. > > On Jun 29, 2016 7:47 AM, "Antoine Sabot-Durand" < > *antoine at sabot-durand.net* > wrote: > You mean the instance of SeContainerInitializer obtained thru > getInstance() ? > Le mer. 29 juin 2016 ? 13:26, John D. Ament <*john.d.ament at gmail.com* > > a ?crit : > Antoine, > > Looks like we may have missed one of the earlier comments, about reusing > the instance vs creating a new one each time. > > John > > On Wed, Jun 29, 2016 at 7:23 AM Antoine Sabot-Durand < > *antoine at sabot-durand.net* > wrote: > Hi all, > > I just push changed decided in yesterday meeting to PR 290[1]. Please > review them and give a +1 on it if you're ok for the merge. > Generated version of the spec is available here [2]. > > Antoine > > [1]: *https://github.com/cdi-spec/cdi/pull/290* > > [2]: > *https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se* > > > _______________________________________________ > 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. > _______________________________________________ > 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. > > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/b7dde26f/attachment.html From antoine at sabot-durand.net Wed Jun 29 11:10:24 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Wed, 29 Jun 2016 15:10:24 +0000 Subject: [cdi-dev] Last review on PR 290 (SE bootstrap) In-Reply-To: References: Message-ID: Correct me if i'm wrong John. Are you suggesting that SeContainerInitializer#getInstance() should return always the same initializer? I don't remember this comment. What would be the advantage of that instead of getting a new one at each call ? If we want to have the SeContainerInitializer reusable we should probably add a kind of 'reset()' method. Wdyt Antoine Le mer. 29 juin 2016 ? 15:07, John D. Ament a ?crit : > Yes. > On Jun 29, 2016 7:47 AM, "Antoine Sabot-Durand" > wrote: > >> You mean the instance of SeContainerInitializer obtained thru >> getInstance() ? >> Le mer. 29 juin 2016 ? 13:26, John D. Ament a >> ?crit : >> >>> Antoine, >>> >>> Looks like we may have missed one of the earlier comments, about reusing >>> the instance vs creating a new one each time. >>> >>> John >>> >>> On Wed, Jun 29, 2016 at 7:23 AM Antoine Sabot-Durand < >>> antoine at sabot-durand.net> wrote: >>> >>>> Hi all, >>>> >>>> I just push changed decided in yesterday meeting to PR 290[1]. Please >>>> review them and give a +1 on it if you're ok for the merge. >>>> Generated version of the spec is available here [2]. >>>> >>>> Antoine >>>> >>>> [1]: https://github.com/cdi-spec/cdi/pull/290 >>>> [2]: >>>> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#bootstrap-se >>>> >>>> _______________________________________________ >>>> 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. >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160629/b8a48e2c/attachment.html From antoine at sabot-durand.net Thu Jun 30 03:20:38 2016 From: antoine at sabot-durand.net (Antoine Sabot-Durand) Date: Thu, 30 Jun 2016 07:20:38 +0000 Subject: [cdi-dev] Closing CDI F2F Doodle on monday Message-ID: Hi all, It's time to decide the final date of the F2F meeting in septembre. So the Doodle to check your favorite date will be closed after the week-end. So if you didn't vote it's still time. If you already voted please double check your choice: http://doodle.com/poll/mby6vkkgdsyd2fg9 Antoine -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20160630/455f6547/attachment.html