Rony G. Flatscher wrote:
...
Also, there is a group of applications and use cases which become
impossible: all classes with are reachable to *any* Java application on
a system that are listed on the process' default environment variable
CLASSPATH. At the moment is seems to be the case that OOo face-2-face to
Java-OOo-extensions hides the CLASSPATH settings from them! [The
behaviour would be comparable to removing the settings of the PATH
environment variable from apps that are deployed via OOo or its
extensions, sort of blinding and deafing them.]
...
Well, personally I don't mind ignoring the CLASSPATH variable.
Requiring desktop GUI users to deal with command-line oriented settings
is a non-starter in many situations.
I think for cross-platform desktop use, directing folks to configure the
OOo:Preferences:Java panel is more manageable.
And if you want to configure the system classpath, then using the
Optional Package mechanism is better.
http://java.sun.com/j2se/1.5.0/docs/guide/extensions/spec.html#installed
My pet peeve about the OOo Java Preferences though is that it only
permits a *single* configuration for each installed JRE. That means if
I have different command line options (for normal vs. debug for
example), they have to be reentered every time rather than choosing a
radio button.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
