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=4002301#4002301
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002301
When used with JBoss Retro, we will replace access to Constructor.getGenericParameterTypes() with a call to some other class that does this. We will also replace all occurrences of java.lang.reflect.Type with org.jboss.lang.reflect.Type etc.
The "some other class that does this" will need to use javassist to get hold of the generic info, similarly to how the JBoss Retro AnnotationHelper uses javassist to get hold of the annotations from the bytecode attributes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002298#4002298
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002298