Details

    • Type: Bug Bug
    • Status: Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 2.8.0.Final
    • Fix Version/s: 2.8.1.Final, 3.0.0.Alpha4
    • Component/s: JCR
    • Labels:
      None
    • Environment:
    • Affects:
      Compatibility/Configuration
    • Similar Issues:
      Show 10 results 

      Description

      According to forum discussion it looks like Modeshape JCR 2.8 is not able to load the correct logger bundle for default Locale en_US.

      10:35:10,153 INFO  [org.modeshape.jcr.RepositoryQueryManager] (modeshape-start-repo-4-thread-1) <Problems were encountered while localizing internationalization class org.modeshape.jcr.JcrI18n to locale "en_US" >
      

      This doesn't have any affect on the Jcr Repository itself under read/write/query operations.

        Gliffy Diagrams

          Activity

          Hide
          Randall Hauch added a comment -

          Probably the best way to handle this is to log a warning if a bundle can't be found for the current local, but an error if the default bundle can't be found.

          Show
          Randall Hauch added a comment - Probably the best way to handle this is to log a warning if a bundle can't be found for the current local, but an error if the default bundle can't be found.
          Hide
          Horia Chiorean added a comment -

          Added explicit logging of warnings & errors in case I18n bundles can't be located

          As a sidenote: I've looked at the discussion thread and I agree with Randall: the only way that error message can appear for JcrI18n.properties is if the default .properties file (the one provided in the jar) is renamed explicitly or if a ClassLoader is used which cannot load that file from the -jcr jar.

          Show
          Horia Chiorean added a comment - Added explicit logging of warnings & errors in case I18n bundles can't be located As a sidenote: I've looked at the discussion thread and I agree with Randall: the only way that error message can appear for JcrI18n.properties is if the default .properties file (the one provided in the jar) is renamed explicitly or if a ClassLoader is used which cannot load that file from the -jcr jar.
          Hide
          Horia Chiorean added a comment -

          The commit can be cherry picked into 3.x as well

          Show
          Horia Chiorean added a comment - The commit can be cherry picked into 3.x as well
          Hide
          Randall Hauch added a comment -

          Merged into the '2.x' branch and cherry-picked onto the 'master' branch.

          Show
          Randall Hauch added a comment - Merged into the '2.x' branch and cherry-picked onto the 'master' branch.

            People

            • Assignee:
              Horia Chiorean
              Reporter:
              Ove Ranheim
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development