Trail: Security Features in Java SE
Lesson: Implementing Your Own Permission
The HighScorePermission Class
Home Page > Security Features in Java SE > Implementing Your Own Permission
The HighScorePermission Class
The HighScorePermission class defines the permission that TerrysGame needs to update the user's high score.

All permission classes should subclass from either java.security.Permission or java.security.BasicPermission. The basic difference between the two is that java.security.Permission defines more complex permissions that require names and actions. For example, a java.io.FilePermission extends from java.security.Permission, and requires a name (a filename), and actions allowed for that file (read/write/delete).

In contrast, java.security.BasicPermission defines simpler permissions that only require a name. For example, java.lang.RuntimePermission extends from java.security.BasicPermission and simply needs a name (like "exitVM"), which allows programs to exit the Java Virtual Machine.

Our HighScorePermission is a simple permission, and hence can be extended from java.security.BasicPermission.

Often, the method implementations in the BasicPermission class itself do not need to be overridden by its subclasses. That is the case with our HighScorePermission, so all we need to implement are the constructors, which just invoke the superclass constructors, as shown in the following:

/*
 * Copyright (c) 1995 - 2008 Sun Microsystems, Inc.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 *   - Redistributions of source code must retain the above copyright
 *     notice, this list of conditions and the following disclaimer.
 *
 *   - Redistributions in binary form must reproduce the above copyright
 *     notice, this list of conditions and the following disclaimer in the
 *     documentation and/or other materials provided with the distribution.
 *
 *   - Neither the name of Sun Microsystems nor the names of its
 *     contributors may be used to endorse or promote products derived
 *     from this software without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
 * IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
 * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
 * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
 * PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
 * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
 * NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */ 

package com.scoredev.scores;

import java.security.*;

public final class HighScorePermission extends BasicPermission {

    public HighScorePermission(String name)
    {
	super(name);
    }

    // note that actions is ignored and not used,
    // but this constructor is still needed
    public HighScorePermission(String name, String actions) 
    {
	super(name, actions);
    }
}
Previous page: The HighScore Class
Next page: A Sample Policy File