JBoss.orgCommunity Documentation
eXo Platform comes with a pre-configured PortalContainer named "portal". The configuration of this portal container ties the core and the extended services stack. The default Portal Container is started from portal.war and naturally maps to the /portal URL.
The GateIn extension mechanism lets you extend the portal context easily. With this feature, you only need to make your desired modifications on your extension, but NOT on the portal.war. As a result, your upgrades will become simple as your extension.war is totally independent of the portal.war.
This extensibility is achieved via 2 advanced features of the PortalContainer:
A unified ClassLoader: any classpath resource, such as property files, will be accessible as if it was inside the portal.war.
This is valid only for resources but not for Java classes.
A unified ServletContext: any web resources contained in your extension.war will be accessible from /portal/ uri.
For more details on how to make a simple extension for a "portal" container, see the Register Extension section.