logging apis: setLevel methods should check for null level

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P4
    • 1.4.0
    • Affects Version/s: 1.4.0
    • Component/s: core-libs
    • None
    • beta
    • x86
    • windows_nt
    • Verified


      This was brought to my attention by Paul Visotsky.

      The LogManager.setLevel and Handler.setLevel methods should
      check for null levels and throw a NullPointerException.

      Logger.setLevel() already seems to do the right thing.
      LogRecord.setLevel() should allow null.

      graham.hamilton@Eng 2000-10-02

            Assignee:
            Graham Hamilton (Inactive)
            Reporter:
            Graham Hamilton (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: