Summary thus far:<div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8">1. Coin a well-defined set of context lifecycle events to go in Weld Extensions</div><div>    @Application @Initialized Event (and perhaps one per scope annotation?)</div>
<div>2. Use observers based on these events to get startup behavior rather than @Startup components</div><div>    @Observes @Application @Initialized E (what&#39;s the event type?)</div><div>3. Implement event firing in appropriate Seam module (as it has hooks to the boundaries)</div>
<div>    Servlet module already has these hooks in place, just leverage them</div><div>4. Provide a @ClusterScoped annotation &amp; context impl somewhere in Seam 3 (which module?)</div><div><br></div><div>-Dan<br><br>-- <br>
Dan Allen<br>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>
</div>