On Wed, Oct 20, 2010 at 5:49 AM, Pete Muir <pmuir(a)redhat.com> wrote:
Doing it in the CDI container startup callbacks is not correct as
the
container is not fully initialised. For Seam 3.0 you will need to use an EJB
3.1 singleton (which provides an application startup callback), or listen to
servlet callbacks (we may need to fix the ordering of the Seam servlet
listeners outside of JBoss AS/GF). Doing this through events also addresses
your "transient startup scope" as you can simply declare your bean
dependent, meaning it will be destroyed after the observer invocation is
complete.
Duh Dan ;) I realized after thinking about this a bit more that that's
exactly the purpose of a dependent-scoped observer :) My mind wasn't all
there on that one.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen