...
Most SCA applications will be packaged as one or more JARs. In addition to including , which contain application classes and artifacts, a . A JAR -based contribution may contain an requires an contribution manifest file (sca-contribution.xml manifest file xml ) in the META-INF directory. The manifest file contains contribution metadata, including a list of deployable composites. Deployable composites are those composites that are contained in the contribution which are to be deployed to a domain. A contribution may contain other composites but if they are not marked as deployable, they may not be directly included in the domain (i.e. they may only be used by a deployable composite). An example sca-contribution.xml file is shown below:
...
<contribution xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912" xmlns:sample="urn:tempuri.org">
<deployable composite="sample:TheComposite"/>
</contribution>
Applications often require third-party libraries.
Fabric3 supports two ways of packaging and deploying these libraries used by a contribution: by embedding them in the JAR; and importing them from another contribution. Similar to WARs, Fabric3 allows contribution JARs to bundle third-party libraries by placing their JARs in the META-INF/lib directory of the contribution. Any JAR placed in the META-INF/lib directory directory, which in turn will be made available on the contribution classpath. Imports are discussed in XXXXXXXXXXXXXXX.
WAR Contributions
Fabric3 supports packaging contributions as WAR files. WAR contributions behave like JAR contributions except the SCA manifest in is placed in WEB-INF. In addition, libraries and classes in WEB-INF/lib and WEB-INF/classes respectively are placed on the contribution classpath. WAR contributions are used for deploying web applications to a domain.
...