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

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Mon Jul 22 09:22:30 EDT 2013

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

RH Bugzilla Integration commented on JBSEAM-5086:

Marek Novotny <mnovotny at redhat.com> changed the Status of [bug 903177|https://bugzilla.redhat.com/show_bug.cgi?id=903177] from ASSIGNED to CLOSED
> 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

More information about the seam-issues mailing list