Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-1874

OperationTracker description logging improvement

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: In Progress
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.3, 5.4
    • Fix Version/s: None
    • Component/s: tapestry-ioc
    • Labels:

      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:

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              jkemnade Jochen Kemnade
              Reporter:
              denis.stepanov Denis Stepanov

              Dates

              • Created:
                Updated:

                Issue deployment