Hi John,
Yes it doesn’t seem to be explicitly written (I’m still looking) but reading at the
beginning of chapter 12, it’s implicit that there’s one container that do one bean
discovery and fire on set of events for type discovered. So IMO, it's implicit that
extensions are not limited to their current archive and have the same « visibility » level
than the CDI container : i.e. the current application.
This said, it couldn’t hurt to write it explicitly.
Antoine
Le 22 févr. 2014 à 21:51, John D. Ament <john.d.ament(a)gmail.com> a écrit :
Hi all,
Quick question. This is mostly from playing around with Weld SE
2.1.2, so I'm not sure if my question is going to be Weld SE specific
or be generally applied.
Looking through the spec, I did not see any obvious indications of
this. What is the scope of the application of an Extension class?
Suppose I had a JAR file that had
META-INF/services/javax.enterprise.inject.spi.Extension with the
contents of some extension class. Should the application of that
extension class apply to all JARs within the same classpath? If that
extension were listed in a WAR file, would it apply to the WAR and all
JAR modules?
John
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev