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

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.5
    • Fix Version/s: 5.0.6
    • Component/s: tapestry-core
    • Labels:
      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).

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        A little checking showed that Log4J prior to 1.2.12 did not support trace level.

        Show
        Howard M. Lewis Ship added a comment - A little checking showed that Log4J prior to 1.2.12 did not support trace level.

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development