In the past few days we have had two support cases concerning MyFaces and 4.0.2. When someone tries to run JBoss with an old version of MyFaces they see problems with loading TagLibs like this:

2005-08-19 13:45:14,562 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/tpm].[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
javax.faces.FacesException: /error/404.jsp(6,52) Could not add one or more tag libraries.
at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:411)
at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:280)

Internal links to JBoss cases:
https://na1.salesforce.com/50030000001393G
https://na1.salesforce.com/500300000013Quz

The first case has a war that the customer was trying to run. I was unable to reproduce the error. Instead, I just get a blank screen with no errors. I see the same problem with 4.0.3.

If I manipulate the installation to run using the built-in MyFaces a la 4.0.3 and I remove the MyFaces jars from the war then everything works.

What we need is the ability to completely remove JSF support from the container so that JBoss AS can accomidate web apps that use older versions of MyFaces. This will also assure that JSF applications using the RI will work properly.

To remove JSF support, I tried removing the jars from /jsf-libs and commenting out the "engineOptionsClass" and "tagLibJar0" init-params from the JSPServlet defined in deploy\jbossweb-tomcat55.sar\conf\web.xml. This seemed to have no effect. There must be something else that is not getting disabled.