Jason and jhulford,
Thanks for your advice. I checked into ServletContextListener and it
looks like it should work fine. I'm about to give it a try.
Thanks.
--Jim--
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group,
Hi Jim,
Generally I would register a ServletContextListener with the
application-server (in your case Tomcat) to start and stop background
services. You would register it in your web.xml file:
listener
listener-classcom.company.webapp.MyContextListener/listener-class
/listener
Hope this
Technically, the proper way according to the specs is to not utilize
background threads. Of course, since nobody actually obeys that
proclamation, use a ServletContextListener to start your Thread when
the servlet context is started and stop the thread when the context is
being destroyed. In
I have a GWT application that starts an independent thread and leaves
it running for use by multiple GWT sessions.
It appears that under Tomcat, when I Stop of Undeploy the application,
this thread keeps running. I can't figure out the right way to manage
shutting down the thread when the
