[TAP5-1874] OperationTracker description logging improvement

• Type: Improvement
• Status: In Progress
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 5.3, 5.4
• Component/s: tapestry-ioc
• Labels: desired_for_5.5
• Assignee: Jochen Kemnade
• Reporter: Denis Stepanov
• Created: 14/Mar/12 13:23
• Updated: 14/Jul/16 11:06

Description

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:

Issue Links

• relates to: TAP5-2332 Optimize String concatenation performance