Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Complete Reuse</strong></p> <p>To reuse the JDK logic, you could create a property file within the classpath for each of the known locales (such as test_fr_CA.properties, test_fr.properties, test_en_US.properties, test_en.properties, test.properties). Don't forget the root locale (test.properties) if you want to be able to match to it. Then simply create a resource bundle for the locale in question and inspect it to see the actual locale used.</p> <pre><code>ResourceBundle rb = ResourceBundle.getBundle("test", Locale.FRENCH); System.out.println("Locale used is:"+rb.getLocale().toString()); </code></pre> <p>The files can be created dynamically and cleaned up after the test.</p> <p><strong>High Level Code Replication, Low Level Reuse</strong></p> <p>You could replicate the high level code in <a href="http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7-b147/java/util/ResourceBundle.java#ResourceBundle.getBundleImpl%28java.lang.String%2Cjava.util.Locale%2Cjava.lang.ClassLoader%2Cjava.util.ResourceBundle.Control%29" rel="nofollow">java.util.ResourceBundle.getBundleImpl(...)</a>. This is basically going through looking for a match (using your own matching logic like equal toString() representations) in a candidate list of locales reusing <a href="http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7-b147/java/util/ResourceBundle.java#ResourceBundle.Control.getCandidateLocales%28java.lang.String,java.util.Locale%29" rel="nofollow">java.util.ResourceBundle.Control.getCandidateLocales(...)</a> on the locale in question. If there is no match you get the next fallback locale for the locale in question by reusing <a href="http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7-b147/java/util/ResourceBundle.java#ResourceBundle.Control.getFallbackLocale%28java.lang.String,java.util.Locale%29" rel="nofollow">java.util.ResourceBundle.Control.getFallbackLocale(...)</a> For each fallback locale you try to match a locale in it's candidate list repeating the fallback in a loop until there are no fallback locales left. Note that the root locale will be the last candidate in each candidate list but it should be skipped unless you have exhausted all fallback locales.</p> <p>This method does not require creating files. You use a non-existent baseName in the getCandidateLocales(...) and get FallbackLocale(...) calls and compare each candidate locale to your list of known locales looking for a match.</p> <p>A simple example of this would be like the following:</p> <pre><code> ResourceBundle.Control rbControl = ResourceBundle.Control.getControl(ResourceBundle.Control.FORMAT_PROPERTIES); Locale localeInQuestion = Locale.CHINA; List&lt;Locale&gt; knownLocales = Arrays.asList(new Locale[] {Locale.CANADA_FRENCH, Locale.FRENCH, Locale.US, Locale.UK, Locale.ENGLISH, Locale.ROOT}); String nonExistentBaseName = "bogus"; Locale matchingLocale = null; Boolean reachedRootLocaleMatch = false; outerloop: for (Locale targetLocale = localeInQuestion; targetLocale != null; targetLocale = rbControl.getFallbackLocale(nonExistentBaseName, targetLocale)) { List&lt;Locale&gt; candidateLocales = rbControl.getCandidateLocales(nonExistentBaseName, targetLocale); for (Iterator iterator = candidateLocales.iterator(); iterator.hasNext();) { Locale currentCandidateLocale = (Locale) iterator.next(); if (knownLocales.contains(currentCandidateLocale)) { if (currentCandidateLocale.equals(Locale.ROOT)) { reachedRootLocaleMatch = true; } else { matchingLocale = currentCandidateLocale; break outerloop; } } } } if (matchingLocale == null &amp;&amp; reachedRootLocaleMatch) { matchingLocale = Locale.ROOT; } if (matchingLocale != null) { System.out.println("The matching locale is: "+matchingLocale.toString()); } else { System.out.println("There was no matching locale"); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to reuse Spring or Java's locale lookup code?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmikeatv
    1. USmikeatv
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to reuse Spring or Java's locale lookup code?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COmikeatv, thanks so much for the two solutions. The fake files approach is simple and interesting, but this thing should not be ugly in Java. I like the second approach. However, I did tests and notice something. If I use Locale.CHINA as the locale in question and the known locales has Locale.TAIWAN, the result from your code is en_US from my machine. How come? Locale.TAIWAN should be the one returned, correct? What is the purpose of Locale.ROOT in your code? Thanks a lot!
      singulars
      1. PO
      1. UScurious1
    2. CO@curious1, Locale.CHINA will not resolve to Locale.TAIWAN but it will resolve to Locale.CHINESE. The locales become more general as you go down the candidate list. You drop qualifiers for script, region, and variant until you get the least general match. You don't find "siblings" you find "ancestors".
      singulars
      1. PO
      1. USmikeatv
    3. CO@curious1 I don't have much to say about Locale.ROOT. You might want to look at the [documentation](http://docs.oracle.com/javase/6/docs/api/java/util/Locale.html#ROOT) and know that it is like a default (but not JVM default locale which is the fallback) that corresponds to the resource file with only the basename (like test.properties). If the locale in question is Locale.CHINESE and the JVM default is Locale.US but there is no file test_zh.properties, nor test_en_US.properties, nor test_en.properties, then test.properties will be used if it exists.
      singulars
      1. PO
      1. USmikeatv
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload