[cdi-dev] explicit bean archives discovery-mode 'annotated'

Antoine Sabot-Durand antoine at sabot-durand.net
Fri Mar 6 04:50:08 EST 2015

I often give this solution to people having issue with unsatisfied injection point issue. Of course I could also tell them to check every bean and see if there is a bean defining annotation on all of them but it could be far more fastidious.
Perhaps the solution could be to add a neutral annotation (empty stereotypes) that explicitly declares a bean. The oxymora with “annotated" discovery mode is that it was designed to ease life of user (and beginners) but that it requires to understand what is a bean defining annotation and put one on the bean...

> Le 6 mars 2015 à 08:00, Jozef Hartinger <jharting at redhat.com> a écrit :
> Are you really telling people to use beans.xml with bdm="all" again? Is that based on this particular issue or did you reach the conclusion before based on some other issues?
> On 03/05/2015 02:14 PM, Antoine Sabot-Durand wrote:
>> Yes, that’s why you shouldn’t use annotated discovery mode if you want to do serious stuff in CDI.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/cdi-dev/attachments/20150306/f6089d14/attachment.bin 

More information about the cdi-dev mailing list