Uploaded image for project: 'JBoss WFK 2'
  1. JBoss WFK 2
  2. WFK2-95

Seam2.3 localization settings via component.xml doesn't work

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.2.0.GA, 2.3.0.GA, 2.4.0.GA, 2.5.0.GA
    • Fix Version/s: 2.7.0.GA
    • Component/s: Seam 2
    • Labels:
      None
    • Target Release:
    • Steps to Reproduce:
      Hide

      1. You can alter booking example to use more messages bundles.
      2. Create copy of messages.properties named e.g messages_cs.properties
      3. Rename original messages.properties to messages_en.properties
      4. Add mentioned snippet to components.xml
      5. Build app and deploy (don't forget to check you browser language settings, I used FF)

      Show
      1. You can alter booking example to use more messages bundles. 2. Create copy of messages.properties named e.g messages_cs.properties 3. Rename original messages.properties to messages_en.properties 4. Add mentioned snippet to components.xml 5. Build app and deploy (don't forget to check you browser language settings, I used FF)
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Add com.sun.faces.config.ConfigureListener to web.xml before org.jboss.seam.servlet.SeamListener. You can see https://issues.jboss.org/browse/JBSEAM-4401

      Show
      Add com.sun.faces.config.ConfigureListener to web.xml before org.jboss.seam.servlet.SeamListener. You can see https://issues.jboss.org/browse/JBSEAM-4401
    • Affects:
      Release Notes
    • Release Notes Docs Status:
      Documented as Known Issue
    • Release Notes Text:
      Hide
      When locale-config configuration is used in a Seam application, the following error message is shown in the server container log:

      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.

      As a consequence, locale-config configuration is not taken into account in the application. As a workaround, use com.sun.faces.config.ConfigureListener configuration in the application's web.xml file. As a result of the workaround, the locale configuration works as expected.
      Show
      When locale-config configuration is used in a Seam application, the following error message is shown in the server container log: 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. As a consequence, locale-config configuration is not taken into account in the application. As a workaround, use com.sun.faces.config.ConfigureListener configuration in the application's web.xml file. As a result of the workaround, the locale configuration works as expected.
    • Bugzilla References:

      Description

      Description of problem:

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                manaRH Marek Novotny
                Reporter:
                tremes Tomas Remes
                Writer:
                Sneha Agarwal Kumar
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: