To add to Thomas' comment and CMS Watch's evaluation. Their argument on Enterprise Integration clearly shows they have no idea about features of JBoss Portal. Here is a technical rebuttal to their argument: anonymous wrote : | Enterprise Application Integration combines separate applications into a co-operating federation of applications. | JBoss Portal provides a JSR-168 portlet container which clearly gives you the tool that you need to expose your J2EE applications as portlets and federate them like mentioned above. The Identity Management Module's pluggability and SSO integration helps federate the security aspect of these applications as well. anonymous wrote : | Portals that support complex workflows depend upon queuing services, identity management (particularly for role management), and business rule engines to coordinate multi-step processing. | JBoss Portal integrates well with the JBoss JEMS stack which provides various tools for workflow/business rules - JBPM and Drools. In fact the CMS workflow is built using JBPM Identity Management - JBoss Portal's pluggable Identity Module and support of SSO frameworks Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079666#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...