[cdi-dev] CDI 2.0 first Face to face meeting feedbac
John D. Ament
john.d.ament at gmail.com
Thu Oct 23 07:38:24 EDT 2014
I could see this being problematic for implementations to deal with:
ContainerBoot boot = ...;
BeanManager beanManager1 = boot.initialize();
BeanManager beanManager2 = boot.initialize();
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
On Thu, Oct 23, 2014 at 5:51 AM, Antoine Sabot-Durand <
antoine at sabot-durand.net> wrote:
> What would be the interest of having CDI object to call getBeanManager()
> instead of having the bean manager directly ?
> Le 23 oct. 2014 à 03:13, John D. Ament <john.d.ament at 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?
> On Wed, Oct 22, 2014 at 6:55 AM, Antoine Sabot-Durand <
> antoine at sabot-durand.net> wrote:
>> Hi guys,
>> New post on the blog : Check what was discussed in our last week F2F
>> cdi-dev mailing list
>> cdi-dev at lists.jboss.org
>> 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...
More information about the cdi-dev