Name: elR10090			Date: 10/02/2000



Logging APIs specification (draft 0.49) states:

"setLevel(String, Level)

... (skipped)

The given log level applies to the named Logger (if it exists), and
on any other named Loggers below that name in the naming hierarchy."

and

"The namespace should typically be aligned with the Java packaging
namespace, but is not required to follow it slavishly."

If any "not follow it slavishly" and define some loggers with
exotic names like ".something" or "something..else" with the
empty parts between dots, then the LogManager will not properly
build its loggers tree as the following test shows.

IMHO, the usage of empty parts of a logger names should be straightly
restricted in the spec and accordingly implemented. Unless to the contrary
it should be straightly permitted in spec and the LogManager namespace
algorithm should be fixed.

setlevel003 log:

# Wrong logger "a..b.c" level "1", expected "2"
# TEST FAILED.

setlevel003.java source:

// File: @(#)setlevel003.java   1.1 00/10/02
// Copyright 10/02/00 Sun Microsystems, Inc.  All Rights Reserved

package logging.LogManager.setLevel;

import java.util.logging.*;
import java.util.*;
import java.io.*;

public class setlevel003 {

    final static int PASSED = 0;
    final static int FAILED = 2;
    final static int JCK_STATUS_BASE = 95;
    final static String failMessage = "# TEST FAILED.";

    final static String names[] = {
        "",
        "a",
        "a..b",
        "a..b.c"
    };

    private static boolean testFailed = false;
    private static boolean verbose = false;
    private static Vector loggers = new Vector();

    public static int run(String args[], PrintStream out) {
        verbose = (args.length > 0) && args[0].equals("-v");

        LogManager manager = LogManager.getLogManager();

        for (int i = 0; i < names.length; i++) {
            String name = names[i];
            try {
                loggers.addElement(Logger.getLogger(name));
                if (verbose) {
                    out.println(
                        "logger \"" + name + "\" was successfully added");
                }
            } catch (IllegalArgumentException ex) {
                if (verbose) {
                    out.println(
                        "getLogger: logger \"" + name + "\" has illegal name");
                }
            }
        }

        for (int i = 0; i < names.length; i++) {
            String name = names[i];
            Level level = Level.parse("" + i);
            try {
                manager.setLevel(name, level);
                if (verbose) {
                    out.println("Level " + level + " logger " + name);
                }
            } catch (IllegalArgumentException ex) {
                if (verbose) {
                    out.println(
                        "setLevel: logger \"" + name + "\" has illegal name");
                }
                continue;
            }
            for (int j = i; j < names.length; j++) {
                String subName = names[j];
                Level subLevel = manager.getLevel(subName);
                if (!level.equals(subLevel)) {
                    out.println("# Wrong logger \"" + subName
                        + "\" level \"" + subLevel
                        + "\", expected \"" + level + "\"");
                    testFailed = true;
                }
            }
        }

        if (testFailed) {
            out.println(failMessage);
            return FAILED;
        } else {
            return PASSED;
        }
    }

    public static void main(String args[]) {
        // produce JCK-like exit status.
        System.exit(run(args, System.out) + JCK_STATUS_BASE);
    }
}
 
======================================================================

Name: elR10090			Date: 02/01/2001


This bug affects the following testbase_nsk test:
    nsk/logging/LogManager/setLevel/setlevel003


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