[cdi-dev] Identify a Bean as synthetic?

Matej Novotny manovotn at redhat.com
Fri Feb 24 01:51:22 EST 2017

Not sure I follow here, but as it is now, you can leverage things like ProcessSyntheticAnnotatedType, ProcessSyntheticBean etc.
You can have an observer for those and get notified of added AT, Bean, OM,...

Is that it? Or did you have something else in mind?


----- Original Message -----
> From: "Laird Nelson" <ljnelson at gmail.com>
> To: cdi-dev at lists.jboss.org
> Sent: Thursday, February 23, 2017 9:41:49 PM
> Subject: [cdi-dev] Identify a Bean as synthetic?
> I haven't thought this through yet but I wonder if it would be helpful to
> mark a Bean as synthetic or not—i.e. discovered by means of the "normal"
> bean discovery process, or programmatically added by a portable extension.
> I was mentally working through what it might take to write up a sort of CDI
> reporting mechanism—something that would report on what beans where found,
> where they came from, what interceptors are enabled and why, etc. etc. etc.
> and realized one axis of this would be whether a portable extension was
> involved with certain beans or not.
> Should I file an enhancement/feature request, or is this something that was
> already debated and turned away at some point in the past?
> Best,
> Laird
> _______________________________________________
> 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.

More information about the cdi-dev mailing list