[seam-issues] [JBoss JIRA] (JBSEAM-5086) localization settings via component.xml doesn't work

[Marek Novotny (JIRA)]

     [ https://issues.jboss.org/browse/JBSEAM-5086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny closed JBSEAM-5086.
---------------------------------

      Assignee: Marek Novotny
    Resolution: Deferred


I marked it as Deferred, because order of WAR initialization is not in Seam full competences, but rather application or container competences.

The scanning order of WAR from application point of view can be managed only in web.xml. Loading of the listener _com.sun.faces.config.ConfigureListener_ is done from existence of the Tag Library Definition in WAR or from the _javax.servlet.ServletContainerInitializer_. 

Adding _com.sun.faces.config.ConfigureListener_ before _org.jboss.seam.SeamListener_ is just emphasing that we need to have initialized Mojarra before we do Seam initialization, because there are Seam components which rely on initialized JSF environment.
                
> 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
>            Assignee: Marek Novotny
>             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