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

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

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

Howard M. Lewis Ship commented on TAP5-1874:
--------------------------------------------

Yes, I can see DescribedRunnable and DescribedInvokable and DescribedIOOperation.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)