Important note on customizing lib/*.property files and jars in OJVM
====================================================================

OJVM differs from JavaSE (aka JDK) in the specifics of how the users
can configure the environment. What is normally done in JavaSE using
property files and certain customization jars, in many cases done
differently in OJVM, namely by means of schema resources instead of
files. Notice that all JavaSE property files are shipped so that the
users can know the content of the schema resources and have something
to modify. However, changes made to them on the disk have no effect
unless the resources are loaded. Java,home-relative prefix must be
preserved when the file is loaded with loadjava. Modifications and
Loading can be done from any directory, not necessarily from
java.home. The following describes the specifics.


logging.properties

        See the header comment in HOME/lib/logging.properties.

currency.properties

        Default location is HOME/lib/currency.properties, which can be
        altered using system property java.util.currency.data. Not
        shipped by default. No resource by default.  DBAs load
        required currency.properties into schema SYS:

            loadjava -u <credentials> lib/currency.properties

        and that becomes in-effect for every java user.  Ordinary
        users can load required currency.properties into their own
        schemas with

            loadjava -u <user-credentials> lib/currency.properties

        which takes precedence over SYS resource.

HOME/lib/currency.data

        OJVM does not ship this as file. Loaded as SYS schema resource. 

HOME/lib/localedata.jar

        OJVM does not ship this and does not allow loading of it from
        files system.  The locales are pre-loaded into the VM (part of
        classes.bin)

HOME/lib/security/java.security

        This file is pre-loaded into OJVM SYS as resource and
        predigested for efficiency and security at create java system
        time. Changes made to the file on disk have no effect.  To
        learn about customization of it, read section "Customizing
        Default java.security Resource" in Oracle Database Java
        Developer's Guide.

HOME/lib/security/calendars.properties
HOME/lib/security/hijrah-config-umalqura.properties

        Loaded by default as SYS schema resource. The shipped file has
        no effect unless the corresponding SYS resource is
        dropped. When in need to do a change, DBAs should customize
        calendars by editing the properties file and then loading the
        modified version using loadjava in order to prevent file
        reads.

        Currently, only the SYS resource is in effect - ordinary users
        can not overload that with their own modified variants, as
        possible, for instance, for currency.properties.