A DeployableContainer implementation that can run and connect to a remote(different JVM, same machine) Tomcat 7.0 instance. This implementation has lifecycle support, so the container will be started and stopped as part of the test run.
Container Injection Support Matrix
|@Resource||@EJB||@EJB (no-interface)||@Inject (CDI)||@Inject (MC)||@PersistenceContext @PersistenceUnit|
Default Protocol: Servlet 3.0
Container Configuration Options
|bindHttpPort||int||8080||The HTTP port the server will run on, has to be same as in CATALINA_HOME/conf/server.xml.|
|bindAddress||String||localhost||The host the server will run on, has to be same as in CATALINA_HOME/conf/server.xml.|
|catalinaHome||String||$CATALINA_HOME|| The Tomcat configuration to start.
|javaHome||String||$JAVA_HOME|| The Java runtime to use to start the server.
||String|| -Xmx512m -XX:MaxPermSize=128m
|| JVM arguments used to start the server.
|user||String||Username of the user who has manager-script role. It is set in CATALINA_HOME/conf/tomcat-users.xml.|
|pass||String||Password of the user who has manager-script role. It is set in CATALINA_HOME/conf/tomcat-users.xml.|
|jmxPort||int||8089|| The JMX port used to connect to the running instance, needed for deployment introspection.
||Charset of URL used for deploy/undeploy operations.|
||boolean||true|| Should the server startup console log be piped to the console.
||int||120|| Time to wait before throwing Exception on server startup.
|| Which server configuration file to startup with.
Example of Maven profile setup