views:

238

answers:

2

I want to create a bean that has start() and stop() methods. When the webapp's context is active, start() is called during Spring's runtime bootup. When the webapp is undeployed or stopped, the stop() method is invoked.

Is this correct: I annotate my start() method with @PostConstruct and the stop() method with @PreDestroy ?

Normally in the servlet world, I write a ServletContextListener. Would I be able to access the ApplicationContext from the ServletContextListener ?

+5  A: 

You can either annotate your start() and stop() methods as you describe, or you can tell Spring to invoke them explicitly, e.g.

<bean class="MyClass" init-method="start" destroy-method="stop"/>

As for the ServletContextListener, it would not have easy access to the Spring context. It's best to use Spring's own lifecycle to do your bean initialization.

skaffman
+2  A: 

Implement the Lifecycle or SmartLifecycle interfaces in your bean, as described in

http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/beans.html#beans-factory-lifecycle-processor

public interface Lifecycle {
  void start();
  void stop();
  boolean isRunning();
}

Your ApplicationContext will then cascade its start and stop events to all Lifecycle implementations. See also the JavaDocs:

http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/context/Lifecycle.html

http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/context/SmartLifecycle.html

Eero