I tried to get Trinidad to work with Seam/Facelets in a portlet (JSR-168) environment, short research releaved that there're problems with myfaces, facelets, jsf and portlet containers acting together. Most of the problems are how request, response and all sorts of different sessions are handled inside these frameworks. For example, Myfaces makes a lot of assumptions, like casting general Request to implementation specific Requests etc, casting objects to MyFaces Impl classes with additional accessor (like setExternalContext), which don't hold when used along with other frameworks. Thus adding one more (ajax4jsf) is likely to cause additional problems which can only made disappear by adding a lot of unmaintable wrappers and compatabily objects, which in turn make the whole more unstable. Trinidad replaces some of the internal render components (like one for h:commandButton) and i guess ajax4jsf doesn't like that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973764#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...