Override skins with extension

The extension mechanism of eXo Platform 3.5 enables the skin definition to be replaced with the skin resource configured in the extension-deployed web application. This is the example where the CSS path of default portal skin needs to be modified without touching the Platform's files.




<gatein-resources>

  <portal-skin>

    <skin-name>Default</skin-name>

    <css-path>/skin/Defaultskin/Stylesheet.css</css-path>

    <overwrite>false</overwrite>

    <css-priority>0</css-priority>

  </portal-skin>

</gatein-resources>

(The css-path specifies the stylesheet of the new skin.)

Override skins with extension

1. Create a web application whose gatein-resources.xml contains the same content as the above xml block, except the element <css-path> is modified.

2. Ensure that once the server has deployed the artifact, it does not load any web application with gatein-resources.xml configuring the same portal skin.