We tested JBoss 5.0 today - and deployment is "no problem". There are two ways:
(WAY 1) Keep the JSF-implementation that is used by default for CaptainCasa web applications - this is the reference implementation of Sun/Javasoft.
In this case: you need to
(A) add the following context-param to your web.xml
(B) remove xerces-2.8.1.jar from your WEB-INF/lib
Code:
<web-app xmlnssi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee <a href="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" target="_blank" rel="nofollow">http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd</a>"
id="WebApp_ID"
version="2.5">
...
...
</welcome-file-list>
<!-- Deployment on JBoss... -->
<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
</context-param>
<filter>
... ...
(WAY 2) you use the JBoss JSF implementation. In this case you do not have to update the web.xml but you need to remove...:
> xerces-2.8.1.jar
> jsf-api.jar
> jsf-impl.jar
from your WEB-INF/lib directory.
Hmm: in principal we recommend to use (WAY 1) - because that's the environment you develop in... - and the probability of "deployment surprises" is lowest.
Björn