]
Stan Silvert commented on JBAS-4383:
------------------------------------
I'm not sure what you mean by "how this works now". The way it works will
change in AS6, but for 4.2 and 5.x it just bypasses the initialization of the built-in JSF
implementation. That's why you need to stick with default classloading because you
need the impl in WEB-INF/lib to be found first.
See
Allow a different JSF implementation to be packaged in the WAR
--------------------------------------------------------------
Key: JBAS-4383
URL:
https://jira.jboss.org/jira/browse/JBAS-4383
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JSF
Affects Versions: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR2
Reporter: Stan Silvert
Assignee: Stan Silvert
Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-5.0.0.CR1
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: