The way the container classpath is managed in all JBoss 7.x containers and all WildFly containers is slightly different from most others.
In order to add the container classpath to the JBoss / WildFly container, CARGO takes the below steps:
modules/org/codehaus/cargo/classpathsubdirectory of the container home
module.xmlfile is created with the below rule for dependencies:
javax.transaction.apiand the first JAR
During deployment, 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