Re: [cdi-dev] CDI 2.0 first Face to face meeting feedbac
I could see this being problematic for implementations to deal with:
ContainerBoot boot = ...;
BeanManager beanManager1 = boot.initialize();
CDI.current();
BeanManager beanManager2 = boot.initialize();
CDI.current();
I see the second call to CDI.current() failing, since it should end up
bound to a thread. If we instead return back a reference to CDI here, we
know which instance we're dealing with and avoid the underlying threading
problem.
John
On Thu, Oct 23, 2014 at 5:51 AM, Antoine Sabot-Durand <
antoine(a)sabot-durand.net> wrote:
What would be the interest of having CDI object to call
getBeanManager()
instead of having the bean manager directly ?
Antoine
Le 23 oct. 2014 à 03:13, John D. Ament <john.d.ament(a)gmail.com> a écrit :
Hi Antoine,
For the SE feature, I think the return type on the initialize() methods
should be CDI instead of BeanManager. What do you think?
John
On Wed, Oct 22, 2014 at 6:55 AM, Antoine Sabot-Durand <
antoine(a)sabot-durand.net> wrote:
> Hi guys,
>
>
> New post on the blog : Check what was discussed in our last week F2F
> meeting.
>
>
> http://www.cdi-spec.org/news/2014/10/20/CDI-2_0-first-face-to-face-meetin...
>
> Regards,
>
> Antoine
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
> Note that for all code provided on this list, the provider licenses the
> code under the Apache License, Version 2 (
> http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas
> provided on this list, the provider waives all patent and other
> intellectual property rights inherent in such information.
>
Attachments:
- attachment.html (text/html — 3.1 KB)