Spring Boot应用中MessageSource回退至指定Locale的技术咨询

Hey there! Let's figure out how to configure your ReloadableResourceBundleMessageSource to fall back to a specific target Locale (like en_US) instead of relying on the default fallback chain in your Spring Boot 1.5.9.RELEASE application.

Default Fallback Behavior Recap #

First, let's quickly go over how ReloadableResourceBundleMessageSource works by default:

• When looking up a message for a given Locale (e.g., fr_FR), it checks files in this order: messages_fr_FR.properties → messages_fr.properties → messages.properties
• If fallbackToSystemLocale is enabled (default: true), it will also check the system's default Locale resources before falling back to the base messages.properties

But if you want to force a fallback to a fixed, specific Locale whenever the requested Locale's message isn't found, here are two reliable approaches:

Approach 1: Set a Default Locale and Disable System Locale Fallback #

This is the simplest method if you just want to define a static fallback Locale. Use the setDefaultLocale() method along with disabling system locale fallback:

@Bean
public MessageSource messageSource() {
    ReloadableResourceBundleMessageSource messageSource = new ReloadableResourceBundleMessageSource();
    messageSource.setBasename(translationsPath); // e.g., "classpath:messages"
    messageSource.setDefaultEncoding("UTF-8");
    
    // Define your target fallback Locale (e.g., English US)
    messageSource.setDefaultLocale(Locale.US); 
    
    // Disable fallback to system Locale to prioritize your custom default
    messageSource.setFallbackToSystemLocale(false);
    
    return messageSource;
}

How this works:

• When a message isn't found for the requested Locale, it first checks your default Locale's files (e.g., messages_en_US.properties, then messages_en.properties)
• If that still fails, it falls back to the base messages.properties

Approach 2: Custom Parent MessageSource for Strict Fallback #

If you need tighter control (like skipping the base messages.properties entirely and only using your fallback Locale), create a dedicated MessageSource for your target Locale and set it as the parent of your main MessageSource:

@Bean
public MessageSource fallbackMessageSource() {
    ReloadableResourceBundleMessageSource fallbackSource = new ReloadableResourceBundleMessageSource();
    fallbackSource.setBasename(translationsPath);
    fallbackSource.setDefaultEncoding("UTF-8");
    // Force this source to only use your fallback Locale
    fallbackSource.setDefaultLocale(Locale.US);
    fallbackSource.setFallbackToSystemLocale(false);
    // Optional: Disable using the message code as default text if not found
    fallbackSource.setUseCodeAsDefaultMessage(false);
    return fallbackSource;
}

@Bean
public MessageSource messageSource() {
    ReloadableResourceBundleMessageSource messageSource = new ReloadableResourceBundleMessageSource();
    messageSource.setBasename(translationsPath);
    messageSource.setDefaultEncoding("UTF-8");
    // Delegate to the fallback source when messages aren't found
    messageSource.setParentMessageSource(fallbackMessageSource());
    messageSource.setFallbackToSystemLocale(false);
    return messageSource;
}

How this works:

• Your main MessageSource first tries to resolve the message for the requested Locale
• If it fails, it passes the request to the parent MessageSource, which only looks for messages in your specified fallback Locale
• You can tweak the parent's configuration to skip the base properties file if needed

Important Notes for Spring Boot 1.5.x #

• Ensure your translationsPath is correctly formatted (e.g., classpath:messages without the .properties suffix)
• If you use MessageSourceAccessor, it will inherit the fallback configuration of the underlying MessageSource
• Test edge cases: try requesting a message that only exists in your fallback Locale to verify the behavior

内容的提问来源于stack exchange，提问作者skapral