On 9 Dec 2012, at 22:33, Mark Struberg wrote:
Hi folks!
Since I will most probably not be able to attend tomorrows EG meeting I like to add a few
tasks which you folks could please think about.
1.) Since the 1.a 'horizontal' isolation got voted for you folks need to come up
with a detailed solution. There are basically 2 options: 1.a.a.) to live with getting
different instances injected into InjectionPoint with the same type (depending in which
classloader the InjectionPoint is). This will also need to get changed for many
BeanManager methods most probably. And 1.a.b.) to disallow @Alternatives, @Specializes,
Extension handling, etc for classes which 'narrow' beans already defined in parent
ClassLoaders.
I'm still thinking on this, but I prefer the second option basically. It's already
the way it works for specialization. Maybe a slight variant on this.
2.) My Question regarding Producer<T> and InjectionPoint<T>. See the
description over there. Imo the only way atm is to clarify that setProducer and
setInjectionPoint must only be used to create a wrapper which delegates to the instances
resolved via getProducer() and getInjectionPoint() ("...otherwise non-portable
behaviour results."). It's imo just not easily possible to really create an own
Producer from scratch. Wdyt?
3.) Jens pinged me offline to take a look at the current @Transactional discussion, but
for that we need @Nonbinding in the 'new' commons-annotation spec. Pete recently
mentioned that there is new work done in commons-annotation (@Priority).
LieGrue,
strub
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev