logging: class loading should use system class loader

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


      When the LogManager loads classes such as Handlers or configuration classes,
      it currently uses Class.forName(). This means that all the loaded classes
      must be on the boot classpath.

      So to add a new handler class or to add a configuration class, a
      customer has to modify the boot classpath, which is pretty undesirable.

      The LogManager should instead use the system class path.


      graham.hamilton@Eng 2000-09-24

            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: