Performance - more than one Servlet context?

[bwobbones]

Hi,

We are having pretty major performance issues with Richfaces 3.1.6, in the order of a 30% loss in request/response turnaround across our application since we introduced the framework to our MyFaces application.

I think I've narrowed this down to the fact that the filter is pre-processing ALL pages in our application, even ones that don't use RichFaces or A4J tags. Is there an easy way to tell the application that it doesn't need to process all of the pages, only the ones that have a4j: or rich: tags?

I've tried:

* using a url-pattern on the filter - doesn't work.
* separating out the pages that use the ajax enabled tag into their own servlet context but this won't work because its too hard to separate the Richfaces requests from the *.jsf context (myfaces only supports one suffix)

Here's the filter def we are currently using:

 <context-param>
 <param-name>org.richfaces.SKIN</param-name>
 <param-value>blueSky</param-value>
 </context-param>

 <context-param>
 <param-name>org.richfaces.LoadScriptStrategy</param-name>
 <param-value>ALL</param-value>
 </context-param>

 <context-param>
 <param-name>org.richfaces.LoadStyleStrategy</param-name>
 <param-value>ALL</param-value>
 </context-param>

 <context-param>
 <param-name>org.richfaces.COMPRESS_SCRIPT</param-name>
 <param-value>false</param-value>
 </context-param>

 <context-param>
 <param-name>org.richfaces.DEFAULT_EXPIRE</param-name>
 <param-value>2592000</param-value>
 </context-param>

 <filter>
 <display-name>RichFaces Filter</display-name>
 <filter-name>richfaces</filter-name>
 <filter-class>org.ajax4jsf.Filter</filter-class>
 </filter>

 <filter-mapping>
 <filter-name>richfaces</filter-name>
 <servlet-name>Faces Servlet</servlet-name>
 <dispatcher>REQUEST</dispatcher>
 <dispatcher>FORWARD</dispatcher>
 <dispatcher>INCLUDE</dispatcher>
 </filter-mapping>

Just standard. Can anyone help with this? We're about to stop using Richfaces because we can't make it perform.

Greg