Peter, Thanks for the response. The problem with keeping a custom portal application in jboss-portal.sar is that any change in the custom portal application will need the restart of the portal server. However, I think this is a needed feature. If a deployer needs to put his hand in the Portlet package (.war file) to create the instances, that surely breaks the abstraction of a Portlet package which is developed by the Portlet developer. Also the same is achievable through admin portal. But doing it through admin console is not a scalable option if you need to deploy large number of instances of the portal in different boxes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152161#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...