Hi,
Ok i have spent the day looking at this, there are a number of issues that prevented Alfresco from running against the latest Jboss portal (2.2.0)
The first issue is the fact that they now package the MyFaces JAR files inside the embedded TomCat instance in JBoss - which means we need to remove those from our WAR file deployment (thanks to user "petek73" for spotting that). However we use a slightly patched version of MyFaces 1.1.1 so i needed to also overwrite the JAR files in the embedded tomcat with our ones.
The second problem is the exception from the Bootstrap process as mentioned above, which was an issue with logging from Spring where a special logging method needs to be implemented (now fixed) - or adding INFO level to the ROOT log4j appender in JBoss also fixes it.
There are also several issues as JBoss Portal 2.2.0 is quite different from 2.0.0 in that the portal XML deployment descriptors have changed format so the Alfresco portlets will no longer deploy. And also the way that the portal saves attributes in the external HttpSession (hidden by the portletsession) has changed which meant our portal integration was no longer working (which allows us in theory to transparently support both Servlet and JSR-168 Portal containers).
The issues have all been fixed now and I have the latest version of Alfresco working against the JBoss portal 2.20 + JBoss AS 4.0.3sp1.
I will commit the changes shortly. You will either need to wait for the next release to get the updated JBoss bundle or if you want this sooner then you will need to build from the SVN source repo, and overwrite the MyFaces JAR files in the jboss tomcat installation with the ones from our SVN lib dir as mentioned above.
Thanks,
Kevin