: We should be able to use <load-on-startup> for the servlet that is : responsible for : making the core in both Servlet 2.3 and 2.4.
I acctaully thought we were using load-on-startup ... I can't for the life of me figure out why autowarming works since we don't have load-on-startup set to 1. For me it was a question of asthetic code grouping. I didn't want only one of two servlets that both depended on the core existing to init it withought some obvious dependency. Erik: Are you just talking about using <load-on-startup> for a servlet, or is there some other recent addition to he Servlet spec for registering an arbitrary class that should be constructed once per application with init/destroy methods that should be called appropriately ... i can't seem to find anything like that (other then making a servlet with no path mapping) -Hoss
