 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 |
 |
 |
 |
|
||||||||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
|||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
In very rare cases you must supply startup settings to the Java Virtual Machine. In a stand-alone Java application these settings are passed as command-line arguments.
Note
The mechanism described here is for expert Sun Chili!Soft ASP users only.
The startup settings can be passed to the Java Virtual Machine run by the Chili!Bean by specifying them in a configuration file. The default path to the file is as follows:
<CASP_INSTALL_DIRECTORY>/bean/bean.properties
This path can be customized by exporting the CB_PROPERTIES environment variable in the javasetup.sh script to the desired path.
Each line in the configuration file will be passed as an argument to the Java Virtual Machine at startup. For example, configuring the Chili!Bean with file:
#bean.properties
-Dfoo=bar
-Xint
has the same effect as starting the Java Virtual Machine from the command line with the command:
Java -Dfoo=bar -Xint <classname>
The meanings of individual arguments vary with Virtual Machine versions; consult the Virtual Machine's documentation.
Note
Never use this mechanism to change the startup classpath, unless all of the directories and JAR files set in the CLASSPATH by the javasetup.sh script are included.
Copyright 2002 Sun Microsystems, Inc. All rights reserved. Legal Notice.