Fabric3 supports two basic models for deploying to a single-VM environment: single contribution deployment and multi-contribution deployment.
Single Contribution Deployment
Single contribution deployment bundles all application services in a single contribution archive as depicted in the diagram below:
The primary advantage of this approach is simplicity: only a single archive needs to be delivered and deployed. The main drawback of a single contribution is lack of modularity. A single archive bundles all artifacts such as Java classes together. Classes bundled together cannot be individually versioned. Moreover, visibility of implementation classes cannot be restricted using technologies such as OSGi import/export directives (see Modularity for how Fabric3 supports OSGi). For basic applications, the single contribution model may be a reasonable trade-off for the simplicity it offers.
Multi-Contribution Deployment
Multi-contribution deployment involves
