Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-2232

Full review of Seam's log levels

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.1.2.GA
    • Component/s: Core
    • Labels:
      None

      Description

      Debug logging with Seam 2.x is completely useless. The most critical information in the debug log is the instantiation and lookup of components, however, if you enable DEBUG for

      org.jboss.seam.Component, you get thousands of these:

      12:26:06,282 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events
      12:26:06,282 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events
      12:26:06,282 DEBUG [Component] done initializing: org.jboss.seam.core.events

      We need to exclude the event firing from debug logging, even if we hardcode it. And, are these events really useful? I have no idea why and when I'd want to listen to "context variable initialized" events.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  norman.richards Norman Richards
                  Reporter:
                  christian.bauer Christian Bauer
                • Votes:
                  20 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: