You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "Denis Stepanov (Created) (JIRA)" <ji...@apache.org> on 2012/03/14 14:24:38 UTC

[jira] [Created] (TAP5-1874) OperationTracker description logging improvement

OperationTracker description logging improvement
------------------------------------------------

                 Key: TAP5-1874
                 URL: https://issues.apache.org/jira/browse/TAP5-1874
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-ioc
    Affects Versions: 5.3
            Reporter: Denis Stepanov
            Priority: Minor


I like the concept of the OperationTracker, but it would be nice if the operation's description was created only when it's needed. Most of the tapestry code creates the description using the string concatenating or String.format all the time, but it is only used when an error occurs or the debug logging is enabled.

I would suggest to create new interface Operation/OperationInvokable with getDescription method as the replacement of Runnable/Invokable interface:
  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira