It was discovered that when the "Dexo.product.developing=true" parameter was specified, and any portlet archive containing gatein-resources.xml was redeployed, the entire portal container was restarted and the portal restart failed with an exception.
This behavior was counter to the notion that the specified parameter was meant to facilitate faster development by not restarting containers.
The fix implements enhancements to the Kernel Container behavior of "Dexo.product.developing", which results in the portal container restarting when a web archive representing a PortalContainerConfigOwner is redeployed. In Red Hat JBoss Portal, this includes portal archives and portal extension archives deployed under $JPP_HOME/gatein, which cannot be hot re-deployed. Additional fixes have been made which allow portal containers to be correctly restarted. Restarts of this nature can be triggered through JMX operations.