tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1627) Enable OperationTracker to produce debug trace of all operations
Date Fri, 02 Sep 2011 23:18:10 GMT

    [ https://issues.apache.org/jira/browse/TAP5-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096460#comment-13096460

Howard M. Lewis Ship commented on TAP5-1627:

Logging occurs on category/logger org.apache.tapestry5.ioc.Registry

> Enable OperationTracker to produce debug trace of all operations
> ----------------------------------------------------------------
>                 Key: TAP5-1627
>                 URL: https://issues.apache.org/jira/browse/TAP5-1627
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
> The OperationTracker is great at identifying what leads up to an error, but it only keeps
the nested operations leading up to a particular failure; it would be nice if it could emit
debug logging for every operation, including timing for the operation, as a way to identify
what's going on leading up to an error but not tracked in the specific OperationTracker trace.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message