[
https://issues.apache.org/jira/browse/TAP5-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348747#comment-14348747
]
Jochen Kemnade commented on TAP5-1874:
--------------------------------------
If we decide to add those, I suggest we either make use of {{MessageFormat}} or
at least {{CharSequence}} for the description. We could provide a lazy
implementation for that.
> 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, 5.4
> 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)
