The way the container classpath is managed in all JBoss containers version 7 and onwards as well as all WildFly containers is slightly different from most others.
In order to add the container classpath to the JBoss / WildFly container, Codehaus Cargo takes the below steps:
modules/org/codehaus/cargo/classpath
subdirectory of the container homemodule.xml
file is created with the below rule for dependencies:javax.api
and javax.transaction.api
javax.api
, javax.transaction.api
and the first JARDuring deployment, Codehaus Cargo will edit your deployables' META-INF/MANIFEST.MF
file in order to add the property Dependencies
with all the JARs in the container classpath.
As per the logic followed to add these into the JBoss / WildFly container's classpath, these dependencies all start with the prefix org.codehaus.cargo.classpath.