]
Stan Silvert resolved JBAS-4383.
--------------------------------
Resolution: Partially Completed
Unit test for this has only been committed to trunk. It will be committed to the 4.2
branch after GA.
Allow a different JSF implementation to be packaged in the WAR
--------------------------------------------------------------
Key: JBAS-4383
URL:
http://jira.jboss.com/jira/browse/JBAS-4383
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JavaServerFaces
Affects Versions: JBossAS-4.2.0.CR2, JBossAS-5.0.0.Beta2
Reporter: Stan Silvert
Assigned To: Stan Silvert
Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-5.0.0.GA
Prior to JEE5, most developers would bundle a JSF implementation such as MyFaces with the
WAR. With AS 4.2 and 5.0, you should instead rely on the JSF implementation that ships
with the container.
However, for these legacy applications that rely on a particular implementation, we can
disable the built-in JSF implementation as long as you stick with the default classloader
settings. To disable the built-in JSF, you will add this to your web.xml:
<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
</context-param>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: