Name: mgC56079 Date: 11/30/98



There is an inconsistency in the behaviour of some security-constrained methods (such as
FileOutputStream, FileInputStream, FileReader, FileWriter, RandomAccessFile constructors,
System.getProperty, Boolean.getBoolean, Integer.getIntege etc) when handling null arguments.
These methods throw NullPointerException when no security manager is installed
and throw IllegalArgumentException with a security manager.
The problem is than SecurityManager.checkXXX methods throw undocumented IllegalArgumentException
when called with null argument.

Here is a test demonstrating the bug
========== FileWriterTest.java =============
import java.io.*;

public class FileWriterTest {

    public static void main(String[] s) {
        try {
            new FileWriter((String)null);
        }
        catch (Exception e) {
            e.printStackTrace();
        }
        System.setSecurityManager(new SecurityManager());
        try {
            new FileWriter((String)null);
        }
        catch (Exception e) {
            e.printStackTrace();
        }
    }

}
========== sample run =============
java FileWriterTest
java.lang.NullPointerException
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(Compiled Code)
at java.io.FileOutputStream.<init>(Compiled Code)
at java.io.FileWriter.<init>(Compiled Code)
at FileWriterTest.main(Compiled Code)
java.lang.IllegalArgumentException: name can't be null
at java.io.FilePermission.init(Compiled Code)
at java.io.FilePermission.<init>(Compiled Code)
at java.lang.SecurityManager.checkWrite(Compiled Code)
at java.io.FileOutputStream.<init>(Compiled Code)
at java.io.FileOutputStream.<init>(Compiled Code)
at java.io.FileWriter.<init>(Compiled Code)
at FileWriterTest.main(Compiled Code)

======================================================================