[cdi-dev] Enabling programmatic/synthetic decorators added by extension

[Romain Manni-Bucau]

+1, seems it is the way to fix several issues without introducing a lot of
new concepts/API and in term of technical stack it is just standardizing
what is there.


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>

2016-03-02 22:48 GMT+01:00 Mark Struberg <struberg at yahoo.de>:

> ProxyFactory…
>
> I’m really thinking about introducing something like javax.proxy, maybe as
> own sub-spec PDF…
>
> LieGrue,
> strub
>
>
> > Am 02.03.2016 um 16:31 schrieb arjan tijms <arjan.tijms at gmail.com>:
> >
> > Hi,
> >
> > I'm trying to add decorators and/or interceptors to a Bean<T> that's
> added via an extension. There doesn't seem to be any way to add
> interceptors, but decorators seem almost possible.
> >
> > I've added a decorator in the following way:
> >
> >
> > AnnotatedType<AutoApplySessionDecorator> annotatedType =
> beanManager.createAnnotatedType(AutoApplySessionDecorator.class);
> >
> > BeanAttributes<AutoApplySessionDecorator> beanAttributes =
> beanManager.createBeanAttributes(annotatedType);
> >
> > Bean<AutoApplySessionDecorator> bean =
> beanManager.createBean(beanAttributes, AutoApplySessionDecorator.class,
> beanManager.getInjectionTargetFactory(annotatedType));
> >
> > afterBeanDiscovery.addBean(bean);
> >
> > Where the "AutoApplySessionDecorator" is an existing (non-scanned)
> decorator just used as an example.
> >
> >
> > While this seems to work, the problem is with the enablement. @Priority
> is not processed in this way, since it's only read from an AnnotatedType
> that's been added to the deployment (see e.g. in Weld
> org.jboss.weld.bootstrap.BeanDeployer.processPriority(AnnotatedType<?>)).
> >
> > beans.xml is not really an option here due to the static nature of that
> and the fact that the decorator needs to be enabled dynamically here, plus
> that the implementation class of the decorator is a detail I would not like
> to expose to the application.
> >
> >
> > Is there any other way to either enable a (synthetic) decorator
> programmatically, or to add Interceptors to a programmatically added
> Bean<T>?
> >
> > Kind regards,
> > Arjan Tijms
> >
> > _______________________________________________
> > 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/20160302/f001f288/attachment.html