title: Deploying a third party war in a Spring Boot embedded container
body: <p>Pardon if this feels a bit of "necroposting". I looked and found only one similar question with no answers here (<a href="https://stackoverflow.com/questions/19916935/spring-boot-embedded-wars">Spring-Boot Embedded Wars</a>).</p>
  
  <p>I have a service packaged into a spring boot (1.0) container. This service uses activiti (www.activiti.org) to manage some buisiness processes. I am trying to deploy inside the same spring boot container, the war for activiti-explorer. This war has its own web.inf, spring config, et cetera, so it may conflict with the existing spring config, but nonetheless, I'd like to try to deploy that war as it is.</p>
  
  <p>I haven't found any way to do that, and suspect that spring boot doesn't support the deployment of pre-package wars into the embedded container, isn't it?</p>
  
  <p>Just as a warning, I think I can't put the extracted war into the spring-boot jar as I feel it needs a fully functional web container. If spring-boot doesn't offer this functionality, no big deal, we're going to deploy that war on its own tomcat, but it would be handy if it could be.</p>
  
  <p>Thanks</p>
  
  <hr>
  
  <p><em>Update</em>
  Just to clear better, I have an already running Spring Application standalone server, with its own embedded Tomcat.
  Inside the embedded Tomcat I plugged some @Controllers I developed.
  Then I was also able to map a third-party servlet using a ServletRegistrationBean (mapped to /servlet-path).</p>
  
  <p>Now I'd like to do something similar with another war that contains a full fledged web application (it's a vaadin/spring 3.2 application with its own libraries, jsps, static resources ...) and would like to map it to (say) /war-path.</p>
  
  <p>I would like to drop the war in a well known location and deploy it into tomcar with a (say) WarRegistrationBean that would let Tomcat handle all the classloading hurdles (as I mentioned, the war is using spring 3.2 while I'm using 4.0 with spring boot, ...).
  I suspect that this last feature is not supported by spring-boot or - possibly - even out of scope for the project itself.</p>