Why would you want to bundle your own version of the RI with your application? You can do that if you like, but it has some disadvantages:
1) You have to bundle RI jars with every JSF application.
2) You lose resource injection for managed beans.
3) You lose logging integration. So any log messages from the RI will look weird in the Log4J logs.
4) You have to declare a config listener in your own web.xml.
I also don't understand why you would want to bundle your own EL jars. The ones that ship with JBoss are probably more current than what you are using.
I'm not asking to be snide or anything. This is new functionality to JBoss and I'd really like to know if there are legitimate reasons for doing what you are doing. After all, you wouldn't dream of bundling your own JSP compiler in your WAR. Why would you want to bundle your own JSF?
Also, see http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossWithJSFCDDL
I have the same problem
In order to run this version , I have to comment out the following lines from the jbossweb.deployer/conf/web.xml:
my simple question is why should I have this problem from running before trying any web application in jsf or else ?
so when I comment the above listeners, the example in the link in this link above wouldn't work as it gives initialisation problem.
thanks a lot