Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


Deployables are archives (WAR, EAR, etc) that can be deployed in the container


A Deployable class is a wrapper class around a physical archive. Deployable are constructed using a DeployableFactory provided by your container. The reason for this factory is to support container extensions to archives (for example, Tomcat supports context.xml files located in your WAR's META-INF directory, JBoss allows for a jboss-web.xml located in your WAR, etc). You can of course directly instantiate a Deployable implementation (WAR, EAR, ec) but then you won't benefit from container extension support.

The DeployableFactory interface offers different methods for creating Deployable (e.g. DeployableFactory.createEAR(String), DeployableFactory.createWAR(String), etc).

Once you have a Deployable instance wrapping your archive, you'll need to deploy it. This can be done either using Static Deployment or using Hot Deployment.

Example using the Java API

Deploying a WAR in Tomcat 5.x:

Example using the Ant API

Statically deploying a WAR in Tomcat 5.x:

Note: In the future there will be an Ant task to support Hot Deployment.

  • No labels