[ https://jira.jboss.org/browse/JBAS-8100?page=com.atlassian.jira.plugin.sy... ] Stan Silvert resolved JBAS-8100. -------------------------------- Fix Version/s: 6.0.0.M4 Resolution: Done If no FacesServlet, then FacesServlet and mappings will be automatically added if any of the following are true: * WEB-INF/faces-config.xml is found * A specific JSF implementation is specified with the org.jboss.jbossfaces.JSF_CONFIG_NAME context param * An alternate faces-config file is specified with the javax.faces.CONFIG_FILES context param * A META-INF/faces-config.xml file is found inside a jar in WEB-INF/lib * A META-INF/*.faces-config.xml file is found inside a jar in WEB-INF/lib All of these go beyond the current JSF spec. The last four go beyond Mojarra's FacesInitializer. The one thing that the FacesInitializer does that we do not do is to auto-add the FacesServlet when JSF annotations are detected. At this point I'm planning to leave that unimplemented. The main reason is that there are performance concerns about scanning every class in every WAR. Perhaps the new annotation scanner takes care of this concern? The other reason is that this part does appear difficult to implement in the JSF deployer. I'm assuming that this implementation is sufficient because "waking up" JSF is just a matter of specifying the FacesServlet or fulfilling one of the five conditions above. But arguments to the contrary are welcome. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira