Exploded WAR inside an EAR is not deployed

I think there may be a problem with deploying an EAR that contains an exploded WAR. This must have changed between an old version of TomEE because this used to work. I'm using TomEE+ 7.0.2: Here is the application.xml. myapp-ear webExplodedWarDir <- this isn't

Re: Application InstanceManager is null causing crash with RestEasy Provider

I am using the bundled Tomcat 8.0.5 bundled with TomEE7.0.2(plus). I noticed the version of that was 8.0.5 from the startup logs and downloaded the sources. I downgraded my Rest Easy from 3.0.4.Final to 2.3.6.Final (which I was using with an older version of TomEE) and the Instance Manager isn't

Re: Application InstanceManager is null causing crash with RestEasy Provider

Did you try with the tomcat version compatible of tomee (8.5)? Le 13 déc. 2017 19:25, "awmurray" a écrit : > I've been debugging a startup error deploying a WAR in an EAR. > > After downloading the source and debugging, I can see that the Instance > Manager is null

Application InstanceManager is null causing crash with RestEasy Provider

I've been debugging a startup error deploying a WAR in an EAR. After downloading the source and debugging, I can see that the Instance Manager is null which causes line 108 to NullPointerException out. org.apache.catalina.core.ApplicationFilterConfig.java from catalina.jar. The version is Tomcat