anonymous wrote : I don't know what you are talking about, we submitted a patch to Facelets, but we don't own Facelets so i can't tell you if the path is part of any release yet. Can you at least use a meaningful name for the jar with the bridge class and include the patched one in your releases. It Literally is a few lines of changed code in the method: Replace ExternalContext extContext = context.getExternalContext(); with ExternalContext extContext = context.getExternalContext(); | if (extContext.getRequest() instanceof ServletRequest) { | return super.createResponseWriter(context); | } | Will wait with baited breath for the Ajax4JSF JSR-301 fix. This is a major blow to JSR-168 in our shop. I keep having to say, "can't use it in the portal". Portal features for distributed development and integrating various portlets under one cover are very useful but not at the expense of functionality. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047354#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...