<div class="gmail_quote">On Fri, Jan 14, 2011 at 16:57, Mark Struberg <span dir="ltr"><<a href="mailto:struberg@yahoo.de">struberg@yahoo.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Dan!<br>
<br>
The trick with the servlet is neat ;)<br>
<div class="im"><br>
> If you want to know when CDI is done starting up and when application-<br>
> scoped beans are available, that's the AfterDeploymentValidation event.<br>
</div>Oki, this might work in Weld and in OWB, but does the Spec really forces this for any other container too? In other words: can a developer of an Extension _really_ count on it?<br>
<br>
I also believe it is ambiguous, so should I file a CDI spec clarification issue?<br></blockquote><div><br></div><div>You are correct since it should be in the list under "6.7.3. Application context lifecycle" if it's supposed to be available to those observers.</div>
<div><br></div><div>(I was assuming the application-scope was available to extensions during startup because of the sentence in 11.5: "For each service provider, the container must provide a bean of scope @ApplicationScoped and qualifier @Default, supporting injection of a reference to the service provider instance. The bean types of this bean include the class of the service provider and all superclasses and interfaces." But that only means it should be available when the context is available).</div>
<div><br></div><div>-Dan</div><div><br></div></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>