[ https://issues.jboss.org/browse/JBSEAM-5086?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5086: ------------------------------------------------- Marek Novotny <mnovotny(a)redhat.com&gt; made a comment on [bug 903177|https://bugzilla.redhat.com/show_bug.cgi?id=903177] Real issue here is the order of Mojarra initialization in WAR. Everytime you see the following error message "SEVERE [javax.faces] (MSC service thread 1-2) Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup." you are experiencing different order of applicaiton initialization than Seam and your web application will expect. If correct order is processed you couldn't see that error at all. Correct order is when Mojarra is initialized before Seam is processing configuration. The only working way now is to specify com.sun.faces.config.ConfigureListener in web.xml before org.jboss.seam.servlet.SeamListener configuration to strictly get such order AFAIK. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira