Red Hat Bugzilla – Bug 972914
Portlet Skinning in Portal Extension does not work
Last modified: 2013-11-01 04:24:00 EDT
Description of problem:
CSS files defined in Portal Extension Quickstart are not sent to client.
Version-Release number of selected component (if applicable):
JPP 6.1.0 ER01
1. Cold deploy the productized Portal Extension Quickstart:
git clone https://github.com/ppalaga/gatein-portal-quickstart.git
git checkout prod-6.1
mvn clean install
2. Cold deploy ear/target/gatein-portal-extension.ear
3. Visit http://127.0.0.1:8080/portal/classic
For BannerPortlet and HomePagePortlet, the Portal sends CSS files declared in jpp-branding instead of CSS files declared in Portal Extension
For BannerPortlet and HomePagePortlet, the Portal shoudl send CSS files declared in Portal Extension.
When the skin for the whole portal is changed from JppSkin to Default, one would expect to get Default CSS declated in Portal Extension for both BannerPortlet and HomePagePortlet. Actually only BannerPortlet behaves as expected. For HomePagePortlet, the CSS from jpp-branding is sent. Note that BannerPortlet has no definition for Default skin in jpp-branding and to the very opposite, HomePagePortlet has a definition for Default skin in jpp-branding. It seems that jpp-branding always wins.
This seems to be a regression against JPP 6.0 where the CSS were loaded properly from Portal Extension.
This is not a bug in portal. The experienced behavior was caused by a missing entry in configuration.xml dependencies:
*** Bug 974117 has been marked as a duplicate of this bug. ***