Seam @Startup and @AutoCreate equivalents in JSR-299

[viviansteller.vivian.steller.uni-ulm.de]

Hey there!

Quick questions:

• Is there an equivalent to Seam's @Startup annotation (for Session+Application scope) in JSR-299? Or should are there any events that one can observe to get similar behavior?


• Is there an equivalent to Seam's @AutoCreate annotation or is it required at all?

Thanks & cheers,

Vivian

[dan.j.allen]

@AutoCreate is no longer necessary since a bean will always be created when needed. The @AutoCreate was really introduced to avoid ambiguity problems. Since there is rarely any ambiguity problems in Web Beans (meaning you can only possibly be requesting one instance at any injection point) there is no need for it.

The only equivalent to @Startup is that you can watch for the @Deployed Manager event and your bean will end up being instantiated (a dummy observer). However, I'm thinking this would be a good idea for an extension in Seam or Web Beans to just be able to annotate your class.

[gavin.king]

In the current rev:

void onStartup(@Observes @Deployed Manager mgr) { .... }

In the next rev, probably:

void onStartup(@Observes AfterDeploymentValidation event) { .... }

But this change is still under discussion in the EG.

[fortega]

You can observe an event which is triggered when the application is initialized:

void onStartup(@Observes @Initialized WebApplication webApplication){ ... }

If you have multiple beans which need to be started up: I wrote some code which makes it a lot cleaner: http://blog.fortega.be/2011/04/seam-3-weld-alternative-for-startup.html

[pgmjsd]

@Bart - In case anyone wanders across your post (I did), the @Initialized annotation and the WebApplication class come from Seam Servlet.  Took me a little while to find that. :)