Spring's application context prevents other applications from starting in same servlet container?

Two options come to my mind: Run two instances of Tomcat, on different ports. Perform the authentication in a new thread (preferably using an ExecutorService). Thus the "main" thread won't block and the deployment will continue.

Running the two applications in same servlet container is actually requirement so the first option is unfortunately out of the question. I'm trying to avoid boilerplate code for running the "connector" because otherwise it's going to be used just like a normal bean and that would require additional boilerplating to get it back to "normal" state. – Esko Jul 14 '10 at 8:24.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.