readme

来自「《移动Agent技术》一书的所有章节源代码。」· 代码 · 共 845 行 · 第 1/3 页

1.1.7B and is currently available.  For that reason, Java Plug-in 
1.1.1, which includes JRE 1.1.6, will not be updated to include 1.1.7B. 
For more information, see the Java Plug-in overview at the following 
Sun Web site:

    http://java.sun.com/products/plugin/

2.0  EURO SYMBOL SUPPORT 
______________________________________________________________________

In order to take advantage of the euro symbol support, the operating 
system must support the euro symbol. The following sections give 
further information on euro symbol support.

2.1  Platform Support
______________________________________________________________________

Microsoft's support is as follows:

  Windows 95    Microsoft has posted a 'Windows 95 beta 1 euro 
                product update' on its Web site. This update 
                includes fonts and keyboard drivers.

  Windows 98    Contains codepage support for the euro, appropriate 
                fonts and keyboard drivers.

  Windows NT 4  Microsoft has posted a "Windows NT 4.0 euro product 
                update" on their Web site. This update includes 
                codepage support, fonts and keyboard drivers. It is 
                included in Service Pack 4, which can be found at the 
                following Web site:

                  http://www.microsoft.com/support/winnt/default.htm

The encoded Windows core fonts that contain euro support are Times 
New Roman, Courier New, and Arial.

If you need to change your keyboard layout or input locale (see 
Regional Settings or Keyboard on the Control Panel), you should do 
this before installing the appropriate euro product update. The 
Microsoft Euro Symbol FAQ Web page details the keyboard 
layouts that support the euro. If your input locale is EN English 
(United States) use US-International rather than US as the 
keyboard layout. You can then use the key combination right 'ALT' 
key and 5 to enter a euro character.

The Windows code pages that include the euro are:

  1250 Central/Eastern European
  1251 Cyrillic
  1252 Western Europe
  1253 Greek
  1254 Turkish
  1255 Hebrew
  1256 Arabic
  1257 Baltic
  1258 Vietnamese
  874  Thai

The codepage converters for the codepages listed above have been 
modified to support the euro symbol. A number of additional codepage 
converters have been included to support the euro on IBM codepages, 
including those for EBCDIC. A new ISO codepage, ISO8859_15, has also 
been added.

Note:  The default converter for Western Europe locales has been 
       changed from 8859_1 to Cp1252 as Cp1252 supports the euro 
       and 8859_1 does not.

2.2  Unicode Support
______________________________________________________________________

The Unicode character for the euro is u'20ac'.

2.3  New Locales
______________________________________________________________________

A number of new 'ResourceBundle's have been created to support the euro. 
These are:

  LocaleElements_de_AT_EURO
  LocaleElements_de_DE_EURO
  LocaleElements_de_LU
  LocaleElements_de_LU_EURO
  LocaleElements_en_IE_EURO
  LocaleElements_es_ES_EURO
  LocaleElements_fi_FI_EURO
  LocaleElements_fr_BE_EURO
  LocaleElements_fr_FR_EURO
  LocaleElements_fr_LU
  LocaleElements_fr_LU_EURO
  LocaleElements_it_IT_EURO
  LocaleElements_nl_BE_EURO
  LocaleElements_nl_NL_EURO
  LocaleElements_pt_PT_EURO

The method java.util.Locale.getDisplayVariant() has been modified 
to lookup the localized name of the euro locale (in all cases, 
"Euro") from the resource data.

2.4  Collation of Currency Symbols
______________________________________________________________________

Collation of currency symbols traditionally follows the English 
collation order of the symbol name. Thus 'cent' is followed by 'dollar.' 
According to this scheme, the euro symbol will sort immediately following 
the dollar and dong currency symbols and before the French franc.

2.5  Existing Java Programs
______________________________________________________________________

Existing Java programs that support the euro symbol will run as before, 
with the exception of changes brought about by any new or altered 
default codeset converters. Programs can use the following code to get 
a locale that uses the euro from one that does not.

  Note:  This code will only work for those locales that support the 
         euro.

  if (source.getVariant().indexOf("EURO") >= 0)
    newLocale = source;
  else
    newLocale = new Locale(source.getLanguage(), source.getCountry(),
      source.getVariant().length()>0 ? (source.getVariant() + "_EURO") : "EURO");

3.0  USING JINSIGHT
______________________________________________________________________

This Developer Kit is instrumented for the Jinsight performance 
monitoring tool from Alphaworks. If you install Jinsight, you should 
not replace or update any Developer Kit files.

4.0  USING THE DEVELOPER KIT 
______________________________________________________________________

The following sections give information on using the Developer Kit.

4.1  Specifying the Path to a Tool
______________________________________________________________________

The main Developer Kit tools are Windows programs that are run from a 
command line. After installing the Developer Kit software, you run 
a tool by typing its name in the command line with a filename as 
an argument. 

If you double-click on the compiler "javac" icon, the compiler will 
briefly open and immediately close a DOS window. This is because you 
cannot run the javac tool through a graphical user interface (GUI).

4.2  Setting PATH and CLASSPATH
______________________________________________________________________

You can specify the path to a tool either by typing the path in front 
of the tool each time. For example, if the Developer Kit software is 
installed at C:\jdk1.1.7, you can compile a file named myfile.java, 
by typing the following at the command line:

  C:\jdk1.1.7\bin\javac myfile.java
  
Alternatively, you could add the string C:\jdk1.1.7\bin to your PATH
statement in your startup file or script. Then you could compile the 
file myfile.java file by typing the following at a command line:

  javac myfile.java

The PATH statement enables Windows to find the executable files 
(javac, java, javadoc) from any current directory. To find 
out the current value of your PATH, at the command line type:

  C:\> path

To change the PATH statement on a either a Windows 95 or a Windows 
98 system, edit the AUTOEXEC.BAT file using a text editor or by typing 
the following at a command line:

  C:\> notepad autoexec.bat

Look for the PATH statement in this file. Notice that the PATH 
statement is a series of directories separated by semicolons (;).
Windows looks for programs in the PATH directories in order, 
from left to right. For example, in the following PATH statement,
the java directory is added at the end:

  PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS;C:\JDK1.1.7\BIN

To make the path take effect in that session, type the following 
at a command line:

  C:\>autoexec.bat

To change the PATH statement on a Windows NT system, modify the 
system variable from the System icon in the Control Panel. Click on
the Environment tab and a list of System Variables appears. Click on
Path and modify the variable by adding the desired directory in the
Value text box. To make the path take effect in future sessions, 
click on Set --> Apply --> OK.

The CLASSPATH tells the Java Virtual Machine (JVM) and other 
applications (which are located in the "jdk1.1.7\bin" directory) 
where to find the class libraries, such as classes.zip file (which 
is in the lib directory). By default, the java tools temporarily 
append the following to whatever CLASSPATH you have explicitly set 
in your startup file: 

  .;[bin]\..\classes;[bin]\..\lib\classes.zip

  Where [bin] is substituted by the absolute path to the jdk1.1\bin 
  directory. 

If you keep the bin and lib directories under the same parent 
directory level the executable files will find the classes.  You 
need to set the CLASSPATH only if you move classes.zip or want to 
load a different library (such as one you develop).
    
  Note:  If you want to develop in both versions 1.0.2 and 1.1.7 
         of the Developer Kit, you must set CLASSPATH and PATH 
         separately for each one. To run both versions simultaneously, 
         you can run each in separate DOS windows. If you are running 
         only one at a time, you can write a batch script to switch the 
         values of CLASSPATH and PATH.

The CLASSPATH is not required, but if it is set, it may need to be unset.
To see if it is currently set, type:

  C:\>set

This lists all of the environment variables. CLASSPATH will not 
appear if it is not set. If it is set, you can unset the current 
value by setting it to no value:

  C:\> set CLASSPATH=

If you want the change to be permanent, edit your startup file 
(autoexec.bat) or script and remove the path to the Java platform 
classes from the CLASSPATH environment variable.  

4.3  Running Applets with the Applet Viewer
______________________________________________________________________

Applet Viewer allows you to run one or more applets that are called by
reference in a Web page (HTML file) using the APPLET tag. The
Applet Viewer finds the APPLET tags in the HTML file and runs the
applets, in separate windows, as specified by the tags.

Because Applet Viewer is for viewing applets, it cannot display an 
entire Web page that contains numerous HTML tags. It parses only the 
APPLET tag and no other HTML on the Web page.

To run an applet with Applet Viewer, go to a command line and run Applet 
Viewer, passing the file name or URL of the Web page as its argument.

To invoke Applet Viewer on a file-based Web page in Windows, go to the 
directory where you installed the Developer Kit and at the 
command line type:  

  [bin]\appletviewer demo\GraphLayout\example1.html

  where [bin] is substituted by the absolute path to the jdk1.1\bin 
  directory.

To invoke Applet Viewer on a URL-based Web page in Windows, at the  
command line type:

  bin\appletviewer http://java.sun.com/applets/NervousText/example1.html

  4.3.1  Debugging Applets with the Applet Viewer
  ____________________________________________________________________

  You can debug applets using the -debug option of Applet Viewer. When 
  debugging applets, it is best to invoke Applet Viewer from the 
  directory that contains the applet's HTML file.  For example:

     cd demo\TicTacToe
     ..\..\bin\appletviewer -debug example1.html

  You can find documentation on the debugger and its API at the 
  following Sun Web site:

     http://java.sun.com/products/jdk/1.1/debugging/

4.4  Class Load Hook
______________________________________________________________________