[ https://issues.jboss.org/browse/CDI-558?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand edited comment on CDI-558 at 11/24/15 3:30 AM: -------------------------------------------------------------------- One use case would be : in Java SE I want to prepare an AnnotatedType to give it as on of the type to discover during container initialization. That's why it can be useful to have a way to create such an AnnotatedType before the container and BeanManager availability. So the built-in bean is not a good idea IMO. If we agree on that I see several solution # Put the class in the spec (I don't like it unless we don't find a better solution) # Use Java service loader like we already do with CDIProvider. The loaded service should be a factory allowing getting an instance for AnnotatedTypeBuilder (yeah a factory of builder). That let us the possibility to add another helpers in it later. # Same as previous but with a classical implementation lookup in classpath. The difference is that service loader is guarantee to still work with java 9 Any other thoughts ? was (Author: antoinesabot-durand): One use case would be : in Java SE I want to prepare an AnnotatedType to give it as on of the type to discover during container initialization. That's why it can be useful to have a way to create such an AnnotatedType before the container and BeanManager availability. So the built-in bean is not a good idea IMO. If we agree on that I see several solution #. Put the class in the spec (I don't like it unless we don't find a better solution) #. Use Java service loader like we already do with CDIProvider. The loaded service should be a factory allowing getting an instance for AnnotatedTypeBuilder (yeah a factory of builder). That let us the possibility to add another helpers in it later. #. Same as previous but with a classical implementation lookup in classpath. The difference is that service loader is guarantee to still work with java 9 Any other thoughts ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)