-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| There is no expected startup order. Neither the Servlet spec nor Tomcat
| define one. You can't rely on the apps starting in any particular order.
Yes, you're right. And I'll expected that behaviour.
I missed to sync one file with the version-contro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I have a strange problem with Tomcat 6.0.16 and the start order of my
webapps. I just switched form 32bit-Windows XP to 64bit-Linux on my
development system. On the Windows system everything works as expected:
ROOT webapp is the first webapp to b
