Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4388607

logging apis: catch up with Public Draft of logging APIs.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 1.4.0
    • 1.4.0
    • core-libs
    • None
    • beta
    • x86
    • windows_nt
    • Verified


      Several changes were introduced in the Public draft of the
      java Logging APIs. The implementation should be updated to
      reflect these changes.

      The ConsoleHandler, FileHandler, MemoryHandler, SocketHandler,
      and StreamHandler classes now use a LogManager "filter" property
      to locate a default Filter class to act as a Filter on the Handler.

      The ConsoleHandler, FileHandler, SocketHandler, and StreamHandler
      classes now use a LogManager "formatter" property to locate a
      default Formatter class to act as the Formatter on the Handler.
      The ConsoleHandler, FileHandler, SocketHandler, and StreamHandler
      classes now use a LogManager "encoding" property to determine a
      default character set encoding for the Handler.

      The javadoc in the class header for each of the Handler classes
      has been revised to be more consistent in describing LogManager
      properties and to be clearer on what default values are used if
      a property is not defined (or is not valid).

      The javadoc in each of the concrete Handler classes (in both
      the class header and in the constructors) has been revised to
      specify that the LogManager properties (or their defaults) are
      used as the default configuration for each Handler, unless
      explicitly specified otherwise in a constructor.

      Removed the (false) assumption that XMLFormatter should always
      use UTF-8. I have been reassured that it is OK to use any
      encoding (including the platform default encoding) provided
      the encoding is specified in the XML header, which we do.

      The following constructors were removed. Most of them had
      originally been added in response to a request to provide
      more consistent constructors. However, now that a richer set
      of properties can be defined in the LogManager configuration,
      this particular set of constructors no longer makes particular
      sense. For example it is unlikely that someone will create a
      SocketHandler and want to use the default properties except
      for Formatter. People are likely to either want a default
      handler configuration, or to override wider sets of the
      configuration properties (especially the properties that
      control where output is sent).
      ConsoleHandler(Formatter)
      FileHandler(Formatter)
      SocketHandler(Formatter)
      StreamHandler(Formatter)



      graham.hamilton@Eng 2000-11-13

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

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: