Details
Description
When the web application running XFire is reloaded, or shut down separately from the application server, there is a big problem in that the Spring beans are not also shut down properly. The Spring framework defines a shutdown hook that beans can implement, destroy() For instance, in our case our destroy() method shuts down extra threads that we have spawned and without this shutdown, these threads remain even though everything else gets removed.
XFireConfigurableServlet starts up the bean application context, but does not currently shut it down when servlet.destroy is called.
I am attaching the proposed patch.
Thanks Jeff. We'll apply this.