Name: krC82822 Date: 08/25/2001


java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)

As Java systems become more complex, particularly in the enterprise domain, a
very large number of System Properties need to be set for software to run
correctly. Presently, this is performed on a per-invocation basis using the
-Dkey=value command line switch. I beleive this simple mechanism is becoming
overloaded, resulting in enormous and clumsy command lines, that are very prone
to user errors.

I propose an partial solution; that the JDK file structure include a persistent
properties file in which developers or system administrators can register
default values that will be included in system properties. In effect, a
properties registry for a Java installation.

Data in this registry might include default values for XML factory classes,
security policies, JNDI namespace factories, and the like. It seems far more
appropriate to configure defaults for these types of settings once, and then
have java systems running on that machine work properly without further effort.

Some further observations:
* It it probably inadvisable to allow such default properties to override
intrinsic system properties.
* An API facility to edit these properties, secured by a Permissions mechanism,
would allow installer to set up properties they depend upon.
* Command line set properties should override default properties.

-----------------

25 Aug 2001, eval1127@eng -- in response to our suggestion that the Preferences
API be considered as an alternative, the user commented:

The preferences API describes an alternative API to access config info than
system properties.

However, it does not appear that a persistent config store, whether
preference- or property- based, will be *implemented* in forthcoming Java
runtimes, which was my rfe.

Also, despite the preferences API, the enormous amount of properties
dependent legacy java code will ensure system properties are widely used for
much time to come. Therefore my rfe is still highly relevant.

(Review ID: 130612)
======================================================================