Unlike JBoss Portal 2.7, GateIn Portal 3.1 doesn’t support extending user profiles by configuration. The Account and Organization portlets need to be replaced.
In order to leverage the built-in portlets, you need to use the GateIn WebUI framework, which isn’t well documented. JSF and the Spring Framework are better alternatives.
header-bg-left-shadow2.gif images in your custom theme need to be changed.
You may also need to change the
jboss-portal.sar/portal-core.war/css/login.css file due to JBPORTAL-467 (vote for it!).
It is probably only going to be fixed if there are enough issues for a 2.7.3 release.
https://jira.jboss.org/jira/browse/JBPORTAL-2467 (vote for it!)
The choice between changing
portal-core.war or creating separate applications is the same as changing existing layouts (1-column or 3-columns) or creating new layouts (2-columns).
The good practice of not tampering with JBoss Portal is recommended.
Oddly enough, that is performed in the portlets, not in the portal.
Refer to the 13.2.2 of the Reference Guide.
Refer to the 3.1 section of the Reference Guide.
https://jira.jboss.org/jira/browse/JBPORTAL-2445 (vote for it!)
You can try to work around with 1.0.7, that worked for me.
Red Hat will continue to focus it’s JBoss Community Portal resources on high performance infrastructure and containers, security and rich application integration, while eXo will be contributing and continuing to evolve their excellent user interface and administration features.
Looks like very good news for the community.