Uploaded image for project: 'Tapestry'
  1. Tapestry
  2. TAPESTRY-1738

Render debugging output is incredibly verbose, and should only be output at the TRACE (i.e. more vebose than DEBUG) logging level

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.0.5
    • 5.0.6
    • tapestry-core
    • None

    Description

      Currently if you enable debug output of your page class (i.e., to see the runtime code enhancement) you also get the incredibly verbose diagnostics for rendering of the page. That logging should be at trace, not debug. I believe commons-logging didn't properly offer a trace level (it merged verbose and debug together as debug).

      Attachments

        Activity

          People

            hlship Howard Lewis Ship
            hlship Howard Lewis Ship
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: