That's not an issue IMO, Personally i abuse of it to initialize stuff wich is needed later but not linked to any other spec
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/16 Mark Struberg <[email protected]> > > > @Startup is perfectly broken as well. Read 4.8.1 > > " 4.8.1 Singleton Initialization ...the container must initialize the > Singleton bean > instance during the application startup sequence...." > > > It does NOT define whether other parts of the container must already be > available. I've noticed that @Startup beans get initialized _before_ the > JSF container is fully booted. > > > What is missing is a general startup order for EE containers. Including > events. > > > LieGrue, > strub > > ----- Original Message ----- > > From: Jean-Louis MONTEIRO <[email protected]> > > To: [email protected] > > Cc: > > Sent: Tuesday, October 16, 2012 9:20 AM > > Subject: Re: @Startup like? > > > > Basically, what has been defined for Singleton beans (@Startup and > > @DependsOn)? > > > > Jean-Louis > > > > 2012/10/16 Romain Manni-Bucau <[email protected]> > > > >> Hi guys, > >> > >> after a talk with Charles i wonder if we couldn't add a kind of > >> @Startup/@LoadOnStartup feature to DS. > >> > >> The idea could be to for the init of some bean with the last cdi event > at > >> startup. > >> > >> It could be used to force some init in standalone (cdictrl) or without > >> being dependent of the environment (JSE, JEE, Web...) > >> > >> wdyt? > >> > >> *Romain Manni-Bucau* > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > >> *Blog: **http://rmannibucau.wordpress.com/*< > >> http://rmannibucau.wordpress.com/> > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > >> *Github: https://github.com/rmannibucau* > >> > > >
