Possible Problems (appeared when testing SpringProcessApplication in Tomcat):

• if class RuntimeContainerDelegate exists more than once, there is more than one instance of it. However, this instance holds the references to all engines in the platform. So it may happen that engines are not visible (and deployment fails).
• One test case should be the deployment of a war file that also embeds the engine libary, but uses a container-managed engine (this setup failed in the Spring test cases)
• Another test case for the same setup, but usage of an embedded engine