<div dir="ltr"><div><div><div>Hi,<br><br></div>I know for those in Europe, especially France or Czech Republic a F2F seems planned even in the same month (Sep) which is why I cannot travel aside from nearly 2 full work weeks that'll cost me and my clients.<br><br></div>Antoine and some of his colleagues have a few sessions related to CDI as such and "somewhat related topics" including Docker, Microservices, etc. Are enough others (I know Anatole has a talk, Otavio also does, at least the one related to JSR 363 I plan to join) from the EG there who have time to meet? Hopefully the JCP gets a room in the Hilton again, otherwise I'm sure we could meet somewhere else.<br><br></div>WDYT?<br><div><div><div><div><div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><p style="margin:0px;border-collapse:collapse"><font size="1" face="arial, helvetica, sans-serif"><span lang="EN-US">Werner</span></font></p><span lang="EN-GB"><div style="font-family:arial,helvetica,sans-serif"><img src="https://docs.google.com/uc?export=download&id=0B8SH8c3pTjKAd3pzZUg0aGN3WUE&revid=0B8SH8c3pTjKANkc2eWlhd0dUenU1ei9FYWszeW5RZ3ZtZytzPQ" width="200" height="76"><br><br></div></span></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Jul 27, 2016 at 7:56 AM, <span dir="ltr"><<a href="mailto:cdi-dev-request@lists.jboss.org" target="_blank">cdi-dev-request@lists.jboss.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send cdi-dev mailing list submissions to<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cdi-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Invitation mise ? jour: CDI weekly meeting - Toutes les<br>
semaines entre 18:00 et 19:00 le mardi (CET) (ASD Perso)<br>
(<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>)<br>
2. Re: Enabling programmatic/synthetic decorators added by<br>
extension (Martin Kouba)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 26 Jul 2016 15:35:55 +0000<br>
From: <a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a><br>
Subject: [cdi-dev] Invitation mise ? jour: CDI weekly meeting - Toutes<br>
les semaines entre 18:00 et 19:00 le mardi (CET) (ASD Perso)<br>
To: cdi-dev <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID: <<a href="mailto:001a11c2832c2272ef05388ba8d0@google.com">001a11c2832c2272ef05388ba8d0@google.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Cet ?v?nement a ?t? modifi?.<br>
<br>
Titre : CDI weekly meeting<br>
Weekly meeting of the CDI EG and other community members discussing CDI 2.0<br>
specification.<br>
Date?: Toutes les semaines entre 18:00 et 19:00 le mardi Paris (modifi?)<br>
Lieu : IRC #cdi-dev channel on freenode<br>
Agenda?: ASD Perso<br>
Participants?:<br>
* Antoine Sabot-Durand- organisateur<br>
* cdi-dev<br>
<br>
D?tails de l'?v?nement :<br>
<a href="https://www.google.com/calendar/event?action=VIEW&eid=XzcxMGpnZ3BrNjEwamliOXA2OHNrNGI5azY0cjM0YmExOGNzajBiOW02MTIzYWgxZzcwb2phZ2hsNm8gY2RpLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=MjQjYW50b2luZUBzYWJvdC1kdXJhbmQubmV0Y2Q1YmEzMjU2NzNhZjM4MTFkMDQ5MWU4MjhiYzg2NWUyYjU4YWJhYg&ctz=Europe/Paris&hl=fr" rel="noreferrer" target="_blank">https://www.google.com/calendar/event?action=VIEW&eid=XzcxMGpnZ3BrNjEwamliOXA2OHNrNGI5azY0cjM0YmExOGNzajBiOW02MTIzYWgxZzcwb2phZ2hsNm8gY2RpLWRldkBsaXN0cy5qYm9zcy5vcmc&tok=MjQjYW50b2luZUBzYWJvdC1kdXJhbmQubmV0Y2Q1YmEzMjU2NzNhZjM4MTFkMDQ5MWU4MjhiYzg2NWUyYjU4YWJhYg&ctz=Europe/Paris&hl=fr</a><br>
<br>
Invitation de Google?Agenda?: <a href="https://www.google.com/calendar/" rel="noreferrer" target="_blank">https://www.google.com/calendar/</a><br>
<br>
Vous recevez ce message ? l'adresse <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>, car vous<br>
participez ? cet ?v?nement.<br>
<br>
Refusez cet ?v?nement pour ne plus recevoir de notifications le concernant.<br>
Vous avez ?galement la possibilit? de cr?er un compte Google ? l'adresse<br>
<a href="https://www.google.com/calendar/" rel="noreferrer" target="_blank">https://www.google.com/calendar/</a> et de d?finir vous-m?me les param?tres de<br>
notification pour l'int?gralit? de votre agenda.<br>
<br>
En transf?rant cette invitation, vous risquez d'autoriser tous les<br>
destinataires ? modifier votre r?ponse ? l'invitation. Pour en savoir plus,<br>
consultez la page suivante?:<br>
<a href="https://support.google.com/calendar/answer/37135#forwarding" rel="noreferrer" target="_blank">https://support.google.com/calendar/answer/37135#forwarding</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20160726/6dc7ad8c/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20160726/6dc7ad8c/attachment-0001.html</a><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: not available<br>
Type: text/calendar<br>
Size: 2031 bytes<br>
Desc: not available<br>
Url : <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20160726/6dc7ad8c/attachment-0002.bin" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20160726/6dc7ad8c/attachment-0002.bin</a><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: invite.ics<br>
Type: application/ics<br>
Size: 2091 bytes<br>
Desc: not available<br>
Url : <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20160726/6dc7ad8c/attachment-0003.bin" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20160726/6dc7ad8c/attachment-0003.bin</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 27 Jul 2016 07:56:48 +0200<br>
From: Martin Kouba <<a href="mailto:mkouba@redhat.com">mkouba@redhat.com</a>><br>
Subject: Re: [cdi-dev] Enabling programmatic/synthetic decorators<br>
added by extension<br>
To: <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
Message-ID: <<a href="mailto:10bcc54a-777a-5931-1738-cdaeb5a7a593@redhat.com">10bcc54a-777a-5931-1738-cdaeb5a7a593@redhat.com</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
For the record - in CDI 2.0 we have<br>
javax.enterprise.inject.spi.Prioritized interface (currently used for<br>
ObserverMethod).<br>
<br>
But since Weld 3.0.0.Alpha13 prioritized custom beans, interceptors and<br>
decorators are also supported, i.e. Weld treats them as if annotated<br>
with @Priority (see also WELD-2000 [1]). I think this approach is also<br>
worth standardizing.<br>
<br>
Martin<br>
<br>
[1]<br>
<a href="https://issues.jboss.org/browse/WELD-2000" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/WELD-2000</a><br>
<br>
Dne 26.7.2016 v 11:59 arjan tijms napsal(a):<br>
> Hi,<br>
><br>
> Just wondering, has there been any progress made for this topic?<br>
><br>
> Having the ability to dynamically add interceptors and/or add them when<br>
> building a Bean<T> using the programmatic APIs would still be incredibly<br>
> useful.<br>
><br>
> Kind regards,<br>
> Arjan Tijms<br>
><br>
><br>
> On Fri, Mar 4, 2016 at 5:18 PM, arjan tijms <<a href="mailto:arjan.tijms@gmail.com">arjan.tijms@gmail.com</a><br>
> <mailto:<a href="mailto:arjan.tijms@gmail.com">arjan.tijms@gmail.com</a>>> wrote:<br>
><br>
> ProxyFactory sounds like a perfect solution indeed.<br>
><br>
> I now got something working, more or less, emphasis on less.<br>
><br>
> I first make a "normal" (but effectively dummy) decorator with<br>
> @Priority available:<br>
><br>
> @Decorator<br>
> @Priority(PLATFORM_BEFORE + 200)<br>
> public abstract class HttpAuthenticationBaseDecorator implements<br>
> HttpAuthenticationMechanism, Serializable {<br>
><br>
> private static final long serialVersionUID = 1L;<br>
><br>
> @Inject<br>
> @Delegate<br>
> HttpAuthenticationMechanism delegateMechanism;<br>
><br>
> @Override<br>
> public AuthStatus validateRequest(HttpServletRequest request,<br>
> HttpServletResponse response, HttpMessageContext httpMessageContext)<br>
> throws AuthException {<br>
> return delegateMechanism.validateRequest(request, response,<br>
> httpMessageContext);<br>
> }<br>
> // ...<br>
> }<br>
><br>
><br>
> Then I create a "dynamic/programmatic" decorator:<br>
><br>
><br>
> public class DynamicHttpAuthenticationDecorator implements<br>
> Decorator<HttpAuthenticationBaseDecorator> {<br>
><br>
> private final Set<Type> types = new<br>
> HashSet<Type>(asList(HttpAuthenticationBaseDecorator.class,<br>
> Object.class));<br>
> private final Set<Type> decoratedTypes =<br>
> singleton(HttpAuthenticationMechanism.class);<br>
><br>
> private final BeanManager beanManager;<br>
> private final InjectionPoint decoratorInjectionPoint;<br>
> private final Set<InjectionPoint> injectionPoints;<br>
><br>
> public DynamicHttpAuthenticationDecorator(BeanManager beanManager) {<br>
><br>
> decoratorInjectionPoint = new DecoratorInjectionPoint(<br>
> HttpAuthenticationMechanism.class,<br>
><br>
> beanManager.createAnnotatedType(HttpAuthenticationBaseDecorator.class).getFields().iterator().next(),<br>
> this);<br>
><br>
> injectionPoints = singleton(decoratorInjectionPoint);<br>
><br>
> this.beanManager = beanManager;<br>
> }<br>
><br>
> public HttpAuthenticationBaseDecorator<br>
> create(CreationalContext<HttpAuthenticationBaseDecorator><br>
> creationalContext) {<br>
> return new AutoApplySessionDecorator(<br>
> (HttpAuthenticationMechanism)<br>
> beanManager.getInjectableReference(decoratorInjectionPoint,<br>
> creationalContext));<br>
> }<br>
><br>
> public void destroy(HttpAuthenticationBaseDecorator instance,<br>
> CreationalContext<HttpAuthenticationBaseDecorator> creationalContext) {<br>
> creationalContext.release();<br>
> }<br>
><br>
> public Set<Type> getTypes() {<br>
> return types;<br>
> }<br>
><br>
> public Set<Type> getDecoratedTypes() {<br>
> return decoratedTypes;<br>
> }<br>
><br>
> public Class<?> getBeanClass() {<br>
> return HttpAuthenticationBaseDecorator.class;<br>
> }<br>
><br>
> public Type getDelegateType() {<br>
> return HttpAuthenticationMechanism.class;<br>
> }<br>
><br>
> public Set<InjectionPoint> getInjectionPoints() {<br>
> return injectionPoints;<br>
> }<br>
> }<br>
><br>
> This Decorator<T> "pretends" that it's for the dummy decorator, via<br>
> the getTypes(), but in create() it returns another actual Decorator.<br>
> Then I create the delegate injection point of that decorator by<br>
> grabbing the @Delegate annotated field from the real decorator,<br>
> wrapping that basically in an InjectionPoint and then using that<br>
> later with beanManager#getInjectableReference.<br>
><br>
> Now after adding this via afterBeanDiscovery.addBean(new<br>
> DynamicHttpAuthenticationDecorator(beanManager)), and it actually<br>
> gets called at runtime (tested on Weld).<br>
><br>
> Disadvantages are a fixed priority and the fact that the dummy<br>
> decorator is called as well.<br>
><br>
> Have to say that implementing<br>
> the javax.enterprise.inject.spi.Decorator interface, especially the<br>
> part for grabbing the @Delegate is quite non-obvious.<br>
><br>
> What do you think, is this guaranteed to work, or did I abuse the<br>
> CDI APIs too much here?<br>
><br>
> Kind regards,<br>
> Arjan Tijms<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On Wed, Mar 2, 2016 at 11:14 PM, Thomas Andraschko<br>
> <<a href="mailto:andraschko.thomas@gmail.com">andraschko.thomas@gmail.com</a> <mailto:<a href="mailto:andraschko.thomas@gmail.com">andraschko.thomas@gmail.com</a>>><br>
> wrote:<br>
><br>
> +1<br>
><br>
> in DeltaSpike we implemented an own mechanism + proxy to invoke<br>
> interceptors for partial beans.<br>
> We will probably enhance this for such usecases or even<br>
> producers: <a href="https://issues.apache.org/jira/browse/DELTASPIKE-1069" rel="noreferrer" target="_blank">https://issues.apache.org/jira/browse/DELTASPIKE-1069</a><br>
><br>
><br>
> 2016-03-02 22:51 GMT+01:00 Romain Manni-Bucau<br>
> <<a href="mailto:rmannibucau@gmail.com">rmannibucau@gmail.com</a> <mailto:<a href="mailto:rmannibucau@gmail.com">rmannibucau@gmail.com</a>>>:<br>
><br>
> +1, seems it is the way to fix several issues without<br>
> introducing a lot of new concepts/API and in term of<br>
> technical stack it is just standardizing what is there.<br>
><br>
><br>
> Romain Manni-Bucau<br>
> @rmannibucau <<a href="https://twitter.com/rmannibucau" rel="noreferrer" target="_blank">https://twitter.com/rmannibucau</a>> | Blog<br>
> <<a href="http://rmannibucau.wordpress.com" rel="noreferrer" target="_blank">http://rmannibucau.wordpress.com</a>> | Github<br>
> <<a href="https://github.com/rmannibucau" rel="noreferrer" target="_blank">https://github.com/rmannibucau</a>> | LinkedIn<br>
> <<a href="https://www.linkedin.com/in/rmannibucau" rel="noreferrer" target="_blank">https://www.linkedin.com/in/rmannibucau</a>> | Tomitriber<br>
> <<a href="http://www.tomitribe.com" rel="noreferrer" target="_blank">http://www.tomitribe.com</a>><br>
><br>
> 2016-03-02 22:48 GMT+01:00 Mark Struberg <<a href="mailto:struberg@yahoo.de">struberg@yahoo.de</a><br>
> <mailto:<a href="mailto:struberg@yahoo.de">struberg@yahoo.de</a>>>:<br>
><br>
> ProxyFactory?<br>
><br>
> I?m really thinking about introducing something like<br>
> javax.proxy, maybe as own sub-spec PDF?<br>
><br>
> LieGrue,<br>
> strub<br>
><br>
><br>
> > Am <a href="tel:02.03.2016" value="+492032016">02.03.2016</a> um 16:31 schrieb arjan tijms<br>
> <<a href="mailto:arjan.tijms@gmail.com">arjan.tijms@gmail.com</a> <mailto:<a href="mailto:arjan.tijms@gmail.com">arjan.tijms@gmail.com</a>>>:<br>
> ><br>
> > Hi,<br>
> ><br>
> > I'm trying to add decorators and/or interceptors to a<br>
> Bean<T> that's added via an extension. There doesn't<br>
> seem to be any way to add interceptors, but decorators<br>
> seem almost possible.<br>
> ><br>
> > I've added a decorator in the following way:<br>
> ><br>
> ><br>
> > AnnotatedType<AutoApplySessionDecorator> annotatedType<br>
> =<br>
> beanManager.createAnnotatedType(AutoApplySessionDecorator.class);<br>
> ><br>
> > BeanAttributes<AutoApplySessionDecorator><br>
> beanAttributes =<br>
> beanManager.createBeanAttributes(annotatedType);<br>
> ><br>
> > Bean<AutoApplySessionDecorator> bean =<br>
> beanManager.createBean(beanAttributes,<br>
> AutoApplySessionDecorator.class,<br>
> beanManager.getInjectionTargetFactory(annotatedType));<br>
> ><br>
> > afterBeanDiscovery.addBean(bean);<br>
> ><br>
> > Where the "AutoApplySessionDecorator" is an existing<br>
> (non-scanned) decorator just used as an example.<br>
> ><br>
> ><br>
> > While this seems to work, the problem is with the<br>
> enablement. @Priority is not processed in this way,<br>
> since it's only read from an AnnotatedType that's been<br>
> added to the deployment (see e.g. in Weld<br>
> org.jboss.weld.bootstrap.BeanDeployer.processPriority(AnnotatedType<?>)).<br>
> ><br>
> > beans.xml is not really an option here due to the<br>
> static nature of that and the fact that the decorator<br>
> needs to be enabled dynamically here, plus that the<br>
> implementation class of the decorator is a detail I<br>
> would not like to expose to the application.<br>
> ><br>
> ><br>
> > Is there any other way to either enable a (synthetic)<br>
> decorator programmatically, or to add Interceptors to a<br>
> programmatically added Bean<T>?<br>
> ><br>
> > Kind regards,<br>
> > Arjan Tijms<br>
> ><br>
> > _______________________________________________<br>
> > cdi-dev mailing list<br>
> > <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a> <mailto:<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
> ><br>
> > Note that for all code provided on this list, the<br>
> provider licenses the code under the Apache License,<br>
> Version 2<br>
> (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For<br>
> all other ideas provided on this list, the provider<br>
> waives all patent and other intellectual property rights<br>
> inherent in such information.<br>
><br>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a> <mailto:<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the<br>
> provider licenses the code under the Apache License,<br>
> Version 2<br>
> (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For<br>
> all other ideas provided on this list, the provider<br>
> waives all patent and other intellectual property rights<br>
> inherent in such information.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a> <mailto:<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the provider<br>
> licenses the code under the Apache License, Version 2<br>
> (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all<br>
> other ideas provided on this list, the provider waives all<br>
> patent and other intellectual property rights inherent in<br>
> such information.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a> <mailto:<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the provider<br>
> licenses the code under the Apache License, Version 2<br>
> (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other<br>
> ideas provided on this list, the provider waives all patent and<br>
> other intellectual property rights inherent in such information.<br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
><br>
<br>
--<br>
Martin Kouba<br>
Software Engineer<br>
Red Hat, Czech Republic<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
<br>
End of cdi-dev Digest, Vol 68, Issue 17<br>
***************************************<br>
</blockquote></div><br></div></div></div></div></div></div></div>