[richfaces-issues] [JBoss JIRA] Updated: (RF-6958) RichFaces and Trinidad compatibility issue on Weblogic 10.1 (and Higher)

RichFaces and Trinidad compatibility issue on Weblogic 10.1 (and Higher) ------------------------------------------------------------------------ Key: RF-6958 URL: https://jira.jboss.org/jira/browse/RF-6958 Project: RichFaces Issue Type: Bug Components: core Affects Versions: 3.3.0 Environment: Weblogic 10.1 (Same on 10.3), JSF 1.2 (RI), RichFaces 3.3.0, Trinidad 1.2.11 Reporter: Maxim Pavlov Assignee: Alexander Smirnov Fix For: Future Trinidad PPR response can not be parsed in browser if a4j filter is enabled. Ajax4jsf builds in response and modyfies the html content. As a result trinidad can not parse the response on the client side. This code below in org.ajax4jsf.webapp.BaseFilter.handleRequest solved the issue but I'm more than sure that it is not the best solution anyway. protected void handleRequest(HttpServletRequest request, HttpServletResponse response, FilterChain chain) throws IOException, ServletException { final String TRININDAD_PPR_FLAG_PARTIAL = "partial"; final String AJAXREQUEST_FLAG = "AJAXREQUEST"; boolean isTrinidadRequest = request.getParameterMap().containsKey(TRININDAD_PPR_FLAG_PARTIAL) && !request.getParameterMap().containsKey(AJAXREQUEST_FLAG); if (!isTrinidadRequest) { if (log.isDebugEnabled()) { log.debug(Messages .getMessage(Messages.FILTER_XML_OUTPUT)); } // Execute the rest of the filter chain, including the // JSP xmlFilter.doXmlFilter(chain, request, response); } else { // normal request, execute chain ... if (log.isDebugEnabled()) { log.debug(Messages .getMessage(Messages.FILTER_NO_XML_CHAIN)); } chain.doFilter(request, response); } }