More of just the best practice on how to promote a portal configuration through dev --> stage --> production. Is the best practice to define your portal in the *-object.xml files (with the limitation of not being able to define roles and accounts)? What happens if you have multiple applications deploying to the same portal instance? Should you have an .ear project that just defines the portal? Or....is there a database migration path that is better? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4078881#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...