JBoss.orgCommunity Documentation
A custom extension contains two mandatory items:
extension webapp contains resources and kernel configurations.
extension activator jar identifies your webapp as a dependency of the portal container.
To see the sample extension package, visit here.
Once you have modified the sample extension to build your own portal, use the maven clean install command to create the archive files.
Deploy your extension in Tomcat
1. Add the sample-ext.war file from the sample/extension/war/target/ to the tomcat/webapps directory.
2. Add the starter folder from starter/war/target/ to the tomcat/webapps directory.
3. Rename the starter directory (unzipped folder) to starter.war.
This will only work if the starter.war is the last .war file to be loaded, so you may need to rename it if your war files are loaded in the alphabetical order.
4. Add the .jar file named exo.portal.sample.extension.config-X.Y.Z.jar from sample/extension/config/target/ to the tomcat/lib directory.
5. Add the .jar file named exo.portal.sample.extension.jar-X.Y.Z.jar from sample/extension/jar/target/ to the tomcat/lib directory.
For the JBoss deployment with more details, refer to the GateIn Reference Guide.