Why not use ResourceBundle instead of Properties?
<p>This is an easy question to which I can't find a concluding answer.</p>

<p>I can load string properties (e.g.: a query for a prepared statement) from a <code>config.properties</code> file. Let's say I want to take the database connection to which to connect.</p>

<p>If I want to take this information from the file, I could do just the following in a class:</p>

<pre><code>    private static final ResourceBundle BUNDLE = ResourceBundle.getBundle("scheduler");
    private static final String DRIVER  = BUNDLE.getString("bd.driver");
    private static final String CONNECTIONURL  =BUNDLE.getString("bd.url");
....
</code></pre>

<p>But instead I've seen that many people recommend using instead Properties, Then I would have to do the same with something like this (if I want to keep the class static and not have a proper constructor):</p>

<pre><code>static {
        prop = new Properties(); 
        try {                prop.load(ReportsDB.class.getClassLoader().getResourceAsStream("config.properties"));
        } catch (IOException ex) {
            Logger.getLogger(ReportsDB.class.getName()).log(Level.SEVERE, null, ex);
            throw new RuntimeException(ex);
        }
    }

    private static final String DRIVER  = prop.getProperty("bd.driver");
    private static final String CONNECTIONURL  = prop.getProperty("bd.url");
</code></pre>

<p>So, why shouldn’t I use the <code>ResourceBundle</code> instead of <code>Properties</code> when the second one is more verbose? </p>
