JBoss.orgCommunity Documentation
The Local Protocol implementation is used by most EE5 compliant containers. It does nothing to the deployment. The Local
Protocol is also used when executing in run mode as client
.
Table 13.1. Packaging rules
@Deployment | Output | Action |
---|---|---|
JavaArchive | JavaArchive | Does nothing. |
WebArchive | WebArchive | Does nothing. |
EnterpriseArchive | EnterpriseArchive | Does nothing. |
The Servlet 2.5 Protocol implementation is used by most EE5 compliant containers. It will attempt to add a war to the deployment.
Table 13.3. Packaging rules
@Deployment | Output | Action |
---|---|---|
JavaArchive | EnterpriseArchive | Create a new EnterpriseArchive , add @Deployment and ServletProtocol as module, the other Auxiliary Archives as libraries. |
WebArchive | WebArchive |
If a web.xml is found, a Servlet will be added, else a web.xml will be added. The Servlet WebArchive will be merged with the Deployment and the Auxiliary Archives added as libraries.
|
EnterpriseArchive | EnterpriseArchive | Same as JavaArchive , but using the @Deployment defined EnterpriseArchive instead of creating a new. |
The Servlet 3.0 Protocol implementation is used by most EE6 compliant containers. It will attempt to add a web-fragment to the deployment.
Table 13.5. Packaging rules
@Deployment | Output | Action |
---|---|---|
JavaArchive | WebArchive | Creates a new WebArchive , adds @Deployment and Auxiliary Archives as libraries. |
WebArchive | WebArchive | Adds @Deployment and Auxiliary Archives as libraries. |
EnterpriseArchive | EnterpriseArchive |
If a single WebArchive is found, the same as for WebArchive is done.
If no WebArchives are found a new one is creates, adds @Deployment
and Auxiliary Archives as libraries. If multiple WebArchives are found, a exception is thrown.
|