How to call a Java method while deploying a WAR [duplicate]

Question

This question already has an answer here:

Using special auto start servlet to initialize on startup and share application data (1 answer)

Closed 4 years ago.

How to call a Java method while deploying a WAR

Answer 1

It's not clear what you mean by "deploy". Is that the moment when the WAR file arrives on the app server? Maybe you gin something up with Ant. Is that when the app starts up? Maybe you can do it with a ServletContextListener.

There's no mechanism for doing so built into any Java EE app server I know of, so you're out of luck if Ant isn't suitable. You need something that does the deploying to do it for you.

What's your purpose for doing so? What does this method do?

Answer 2

Multiple solutions are available to you:

• A ServletContextListener can be used to listen to startup events and execute appropriate actions.
• The same thing can be done using a Servlet, with the load-on-startup attribute. You don't have to map your servlet to a servlet-path and can use it only for startup actions.
• If you are using Java EE 6, you can use an EJB anotated with @Startup, which instanciate the service during startup. A @PostConstruct annotation declares a method to execute after instantiation. Note this works only with EJB singletons.

Answer 3

You can use ServletContextListener

Answer 4

If you want to put this functionality in you web app then right place is ServletContextListener

Implementations of the ServletContextListener interface receive notifications about changes to the servlet context of the Web application of which they are part. The following methods are defined in the ServletContextListener :

public void contextInitialized(ServletContextEvent sce)
public void contextDestroyed(ServletContextEvent sce)

The contextInitialized() method is invoked when the Web application is ready for service and the contextDestroyed() method is called when it is about to shut down. The following code shows how we can use these methods to log the application events:

public void contextInitialized(ServletContextEvent e) {
    e.getServletContext().log("Context initialized");
}

public void contextDestroyed(ServletContextEvent e) {
    e.getServletContext().log("Context destroyed");
}

see example, or you can extend you container/server to monitor, as same as monitor tools.