You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/09/03 01:18:10 UTC
[jira] [Created] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
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
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
[jira] [Closed] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1627.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> 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
> Fix For: 5.3
>
>
> 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
[jira] [Assigned] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1627:
------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
[jira] [Commented] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Assigned] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1627:
------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
[jira] [Commented] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096555#comment-13096555 ]
Hudson commented on TAP5-1627:
------------------------------
Integrated in tapestry-trunk-freestyle #503 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/503/])
TAP5-1627: Enable OperationTracker to produce debug trace of all operations
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1164764
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ComponentInstantiatorSourceImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/log4j.properties
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/IOCMessages.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/ModuleImpl.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/OperationTrackerImpl.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/ReloadableObjectCreatorSource.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/util/InternalUtils.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/resources/org/apache/tapestry5/ioc/internal/IOCStrings.properties
* /tapestry/tapestry5/trunk/tapestry-ioc/src/test/resources/log4j.properties
> 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
> Fix For: 5.3
>
>
> 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
[jira] [Commented] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096555#comment-13096555 ]
Hudson commented on TAP5-1627:
------------------------------
Integrated in tapestry-trunk-freestyle #503 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/503/])
TAP5-1627: Enable OperationTracker to produce debug trace of all operations
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1164764
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ComponentInstantiatorSourceImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/log4j.properties
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/IOCMessages.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/ModuleImpl.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/OperationTrackerImpl.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/ReloadableObjectCreatorSource.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/internal/util/InternalUtils.java
* /tapestry/tapestry5/trunk/tapestry-ioc/src/main/resources/org/apache/tapestry5/ioc/internal/IOCStrings.properties
* /tapestry/tapestry5/trunk/tapestry-ioc/src/test/resources/log4j.properties
> 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
> Fix For: 5.3
>
>
> 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
[jira] [Closed] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1627.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> 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
> Fix For: 5.3
>
>
> 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
[jira] [Commented] (TAP5-1627) Enable OperationTracker to produce
debug trace of all operations
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ 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