[ 
https://issues.jboss.org/browse/JBSEAM-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768482#comment-12768482
 ] 

RH Bugzilla Integration commented on JBSEAM-5086:
-------------------------------------------------

Marek Novotny <[email protected]> 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.
                
> localization settings via component.xml doesn't work
> ----------------------------------------------------
>
>                 Key: JBSEAM-5086
>                 URL: https://issues.jboss.org/browse/JBSEAM-5086
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Integration
>    Affects Versions: 2.3.0.Final
>            Reporter: Tomas Remes
>             Fix For: 2.3.1.CR1
>
>
> Adding following snippet to components.xml does not work as expected:
> <inter:locale-config default-locale="cs" supported-locales="en cs"/>
> And it produces following message in server log after application deployment:
> "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."
> If you check class org.jboss.seam.international.LocaleConfig.java and its 
> initLocaleConfig() method, then you'll notice that application variable 
> resolves always to null in this case, therefore the locales are never set 
> correctly.

--
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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues

Reply via email to