ThreadGroup.uncaughtException isn't sufficient

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P4
    • None
    • Affects Version/s: 1.1.6
    • Component/s: client-libs
    • generic
    • generic



      Name: vi73552 Date: 06/08/99


      ThreadGroup.uncaughtException is ok if the user creates a Thread & chooses which ThreadGroup to put it in, but what about GUI threads & their ThreadGroups? It's my understanding that I can't control anything about those threads or their groups, so I have no way to override the default behavior of uncaughtException.

      One alternative might be to define an interface for handling uncaught exceptions & make the current handler a property of ThreadGroup that can be get & set. (I presume that access to setHandler would be checked.)
      (Review ID: 84071)
      ======================================================================

            Assignee:
            Eric Hawkes (Inactive)
            Reporter:
            Vassili Igouchkine (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: