tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAP5-1874) OperationTracker description logging improvement
Date Tue, 19 Apr 2016 12:25:25 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Kemnade updated TAP5-1874:
---------------------------------
    Labels: desired_for_5.5  (was: )

> 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
>              Labels: desired_for_5.5
>
> 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)

Mime
View raw message