normally, the portal-cms.sar will be nested in jboss-portal.sar so the problem will not exist (coordinated by the build system once all artifacts have been created) I agree that for development we have to find a way to make it more usable. "roy.russo(a)jboss.com" wrote : There are problem with the core-cms: | | 1. You *must* deploy the jboss-portal.sar first, and then the portal-cms.sar. If you do not, the cms will not deploy at all, due to some issues with security/identity. | | 2. If you deploy the portal-cms.sar in a running instance of AS, it will create all the resources. | a. File creation is sloooooow. | b. Also, when you log in to the cmsAdminPortlet, it doesn't show the root directory so you can't do anything. I wouldn't be surprised if this is also related to identity integration. | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002794#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...