Mule can run JavaEE web-apps thanks to its embedded Jetty container.
Look at the Bookstore example that comes bundled with the standalone distribution to see how it is done. This example indeed does deploy two web-apps, bookstore and bookstore-admin inside Mule standalone.
Assuming your web-app is xmlproc.war, the layout you want in your Mule application Zip is:
.
├── mule-config.xml
├── classes
│ ├── <classes and resources from xmlproc/WEB-INF/classes>
├── lib
│ ├── <non-provided libs from xmlproc/WEB-INF/lib>
└── webapps
└── xmlproc
├── <jsps>
└── WEB-INF
└── web.xml
With mule-config.xml:
<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns="http://www.mulesoft.org/schema/mule/core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jetty="http://www.mulesoft.org/schema/mule/jetty"
xsi:schemaLocation="
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/jetty http://www.mulesoft.org/schema/mule/jetty/current/mule-jetty.xsd">
<jetty:connector name="jettyConnector">
<jetty:webapps directory="${app.home}/webapps" port="8083"/>
</jetty:connector>
</mule>
Non-provided libs means you shouldn't embed libs that are found under $MULE_HOME/lib/**.