+1 for new events..but need to wait next spec what about an environment integration? we could have a @javax.ejb.Singleton in JEE, a ServletContainerInitializer or ServletContextListener in web and something on our cdictrl in other cases
*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 Gerhard Petracek <[email protected]> > hi romain, > > currently it depends on the other parts of your application. > e.g. in codi we did it for cdi + jsf. > > we discussed it several times - since AfterDeploymentValidation isn't > enough, the following events should be available in the spec(s) imo: > - ContainerStarted (for special cdi extensions which need to get executed > as soon as the cdi container is ready and before application logic gets > triggered) > - ApplicationStarted (for application specific logic which needs the > guarantee that all containers like cdi, jsf,... are ready) > > regards, > gerhard > > > > 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* > > >
