Deployer, DeploymentUnit, and DeploymentContext have been updated with a deployment type notion coming from the Deployer.
/**
* Get the deployment types associated with this deployment.
* @return set of deployment type names deployers have identified
* in this deployment.
*/
public Set<String> getTypes();
Its up to the deployers to populate this set. Right now we don't make effective use of the Deployer.isRelevant(DeploymentUnit unit) method. If this was implemented to reflect when a deployer would process a deployment the MainDeployerImpl could manage the set. For now, the Abstract* deployers that have a specific type that is seen will add their Deployer.getType value to the set. The type property needs to be set in the deployer configuration for this to have meaning, or its initialization updated.
The standard known types are in a org.jboss.deployers.spi.deployer.StandardDeployerTypes interface:
public interface StandardDeployerTypes
{
/** JavaEE enterprise application archive */
public static final String EAR = "ear";
/** JavaEE client application archive */
public static final String CAR = "car";
/** JavaEE ejb generic archive */
public static final String EJB = "ejb";
/** JavaEE ejb 2.1 and earlier archive */
public static final String EJB2x = "ejb2x";
/** JavaEE ejb 3x archive */
public static final String EJB3x = "ejb3x";
/** JavaEE JPA archive */
public static final String JPA = "jpa";
/** JavaEE resource adaptor archive */
public static final String RAR = "rar";
/** JBoss MC beans archive */
public static final String MCBEANS = "beans";
/** JBoss service archive */
public static final String SAR = "sar";
/** JBoss hibernate archive */
public static final String HAR = "har";
/** Spring archive */
public static final String SPRING = "spring";
/** An OSGi bundle */
public static final String OSGI_BUNDLE = "osgi";
/** The deployment type used if a deployer does not specify anything */
public static final String UNSPECIFIED_TYPE = "unspecified";
}
