Skip to end of metadata
Go to start of metadata

A DeployableContainer implementation that manages the complete lifecycle of an embedded (same JVM) Tomcat 6 Servlet Container. (Keep in mind that only select EE APIs are available in Tomcat 6, such as JNDI and Servlet 2.5). Test archives are adapted to Tomcat's StandardContext API by ShrinkWrap and deployed programmatically.

Container Injection Support Matrix

@Resource @EJB @EJB (no-interface) @Inject (CDI) @Inject (MC) @PersistenceContext @PersistenceUnit
       
CDI support requires use of Weld Servlet and associated configuration. The WAR will have to be unpacked as well in order for Weld to locate the classes. See the following configuration example.

Configuration

Default Protocol: Servlet 2.5

Container Configuration Options

Name Type Default Description
bindHttpPort int 9090 The HTTP port the server should bind to.
bindAddress String localhost The host the server should be run on.
tomcatHome String   Optional location of a Tomcat installation to link against.
serverName String   Optional name of the server
appBase String   Optional relative or absolute path to the directory where applications are deployed (e.g., webapps).
workDir String   Optional relative or absolute path to the directory where applications are expanded and session serialization data is stored (e.g., work).
unpackArchive boolean true Specify if the deployment should be deployed exploded or compressed.

Example of Maven profile setup

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.