No need to deploy portal first anymore, I fixed the problem by adding a dependence of ACL
interceptor over its session factory binder service.
"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=4003388#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...