Deployment (Arquillian Container Test API 1.7.1.Final API)

```
@Documented
@Retention(RUNTIME)
@Target(METHOD)
public @interface Deployment
```
The @Deployment is used to define which methods should be be considered as deployment producers. Arquillian support two types of deployment units, a Archive or a Descriptor.
A deployment represent the isolation level of your test, that being a single JavaArchive or a multi module EnterpriseArchive.
The deployment producer will be executed to create the deployment before the Test run, this to detect environment problems as soon as possible.

Usage Example:
```
 @Deployment
 public static WebArchive create() {
      return ShrinkWrap.create(WebArchive.class);
 }

 @Deployment
 public static Descriptor create() {
      return Descriptors.create(HornetQDescriptor.class);
 }
 
```
Version:

$Revision: $

Author:

Aslak Knutsen

Optional Element Summary

Optional Elements
Modifier and Type	Optional Element	Description
`boolean`	`managed`	Describes whether or not this deployment should be deployed by Arquillian.
`String`	`name`	Name the deployment so you can reference it using the `Deployer` API if managed is false or method is using
`int`	`order`	If multiple deployments are specified against the same target and defined as startup, this control the order of which they will be given to the Container.
`boolean`	`testable`	Defines if this deployment should be wrapped up based on the protocol so the testcase can be executed incontainer.

- Element Detail
  - name
```
String name
```
    Name the deployment so you can reference it using the Deployer API if managed is false or method is using
    
    Returns:
    
    The name of this Deployment
    
    Default:
    
    "_DEFAULT_"
- - managed
```
boolean managed
```
    Describes whether or not this deployment should be deployed by Arquillian.
    
    Default:
    
    true
- - order
```
int order
```
    If multiple deployments are specified against the same target and defined as startup, this control the order of which they will be given to the Container.
    
    Default:
    
    -1
- - testable
```
boolean testable
```
    Defines if this deployment should be wrapped up based on the protocol so the testcase can be executed incontainer.
    
    Default:
    
    true