Yes, I guess it's the same limitation raised by JAX-RS regarding CDI integration: when they are up, it's too late. Now perhaps this use case could be addressed by adding a way to wait for servlet initialization before triggering AfterDeploymentValidation event. <br><div class="gmail_quote"><div dir="ltr">Le jeu. 27 août 2015 à 20:55, arjan tijms <<a href="mailto:arjan.tijms@gmail.com">arjan.tijms@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
On Thu, Aug 27, 2015 at 5:56 PM, Antoine Sabot-Durand<br>
<<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>> wrote:<br>
> This topic (modifying bean meta data at runtime) has been coming and going<br>
> since CDI 1.0.<br>
<br>
Does this also mean that Bean<T> instances can be registered at runtime?<br>
<br>
If so, there's maybe one common use, although it's a pretty restricted<br>
version of "runtime"; the ability to register a Bean<T> and/or do<br>
other things extensions typically do from a ServletContainerListener.<br>
<br>
The reason to do those things from a ServletContainerListener is that<br>
the ServletContext is available then, which in turn allows one to read<br>
WEB-INF/web.xml. There are a number of requests to have the<br>
ServletContext made available in extensions, but that's clearly very<br>
difficult to do.<br>
<br>
So if the ServletContext can't come to extensions, maybe extensions<br>
can be brought to the ServletContext via this way?<br>
<br>
Kind regards,<br>
Arjan Tijms<br>
</blockquote></div>