1

I asked this question earlier: Jersey app-run initialization code on startup to initialize application

Is there any way to run this initialization code after the server has initialized the web app fully ? I am running into a catch-22 problem in that I need the web app fully started by Tomcat before I can run my login call once ?

Community
  • 1
  • 1
Vijay
  • 595
  • 1
  • 13
  • 27

1 Answers1

1

There are a few considerations. First, Jersey is implemented as a servlet, and that's how it gets loaded. The simplest way to decouple servlet startup from servlet context startup is to not load it on startup. Accomplish this by omitting the load-on-startup element from the servlet descriptor in the web.xml. Setting it to a non-positive should also work.

If you must load the servlet on startup but still want to decouple it, which was my case, you'll probably have to write some custom code, which I did. I couldn't think of any other way. Use a listener of some type--a ServletContextListener or Spring ApplicationListener, depending on exactly how your app is set up--to kick off a new thread that will initialize your Jersey servlet by making an HTTP request to it. It feels a little dirty, but like I said, it's the only thing I and my team could come up with.

Ryan Stewart
  • 126,015
  • 21
  • 180
  • 199
  • I ended up doing it with a ServletFilter that made the call on the 1st request and not on other calls. – Vijay Nov 18 '11 at 17:20