|
|
Start of Tutorial > Start of Trail > Start of Lesson |
Search
Feedback Form |
In the previous steps you created an entry in theraypolicypolicy file granting code signed bysusanpermission to read files from theC:\TestData\directory (or thetestdatadirectory in your home directory if you're working on UNIX). Now you should be able to successfully execute theCountprogram to read and to count the characters in a file from the specified directory, even when you run the application with a security manager.As described at the end of the Quick Tour of Controlling Applets
lesson, there are two possible ways you can have the
raypolicyfile be considered as part of the overall policy, in addition to the policy files specified in the security properties file. The first approach is to specify the additional policy file in a property passed to the runtime system. The second approach is to add a line in the security properties file specifying the additional policy file.
You can use a-Djava.security.policycommand-line argument to specify a policy file that should be used in addition to or instead of the ones specified in the security properties file.To run the
Countapplication and have theraypolicypolicy file included, type the following while in the directory containing thesCount.jarandraypolicyfiles:java -Djava.security.manager -Djava.security.policy=raypolicy -cp sCount.jar Count C:\TestData\dataNote: The command should be typed on a single line, with a space between
raypolicyand-cp.The program should report the number of characters in the specified file.
If it still reports an error, something is wrong in the policy file. Use the Policy Tool to check the permission you just created in the previous step, and change any typos or other errors.
You can specify a number of URLs -- including ones of the form "http://" -- inpolicy.url.nproperties in the security properties file, and all the designated policy files will get loaded.So one way to have your
raypolicyfile's policy entries considered by the interpreter is to add an entry indicating that file in the security properties file.The security properties file is located at
Important: If you are running your own copy of the JDK, you can easily edit your security properties file. If you are running a version shared with others, you may only be able to modify the system-wide security properties file if you have write access to it or if you ask your system administrator to modify the file when appropriate. However, it's probably not appropriate for you to make modifications to a system-wide policy file for this tutorial test; we suggest that you just read the following to see how it's done or that you install your own private version of the JDK to use for the tutorial lessons.Windows: java.home\lib\security\java.security UNIX: java.home/lib/security/java.securityThejava.homeportion indicates the directory into which the JRE was installed.To modify the security properties file, open it in an editor suitable for editing an ASCII text file. Then add the following line after the line starting with
policy.url.2:Windows: policy.url.3=file:/C:/Test/raypolicy UNIX: policy.url.3=file:${user.home}/test/raypolicyOn a UNIX system you can alternatively explicitly specify your home directory, as in
Next, in your command window, go to the directory containing thepolicy.url.3=file:/home/susanj/test/raypolicysCount.jarfile, that is, theC:\Testor~/testdirectory. Type the following command on one line:java -Djava.security.manager -cp sCount.jar Count C:\TestData\dataAs with approach 1, if the program still reports an error, something is wrong with the policy file. Use the Policy Tool to check the permission you just created in the previous step, and change any typos or other errors.
Important: Before continuing, you may want to delete the line you just added in the security properties file (or comment it out), since you probably do not want theraypolicyfile included when you are not running the tutorial lessons.
|
|
Start of Tutorial > Start of Trail > Start of Lesson |
Search
Feedback Form |
Copyright 1995-2004 Sun Microsystems, Inc. All rights reserved.