You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (Assigned) (JIRA)" <ji...@apache.org> on 2012/01/26 17:00:39 UTC
[jira] [Assigned] (TAP5-1168) @Track annotation that can be used to
automatically track a component or service method invocation using the
OperationTracker
[ https://issues.apache.org/jira/browse/TAP5-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1168:
------------------------------------------
Assignee: Howard M. Lewis Ship
> @Track annotation that can be used to automatically track a component or service method invocation using the OperationTracker
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1168
> URL: https://issues.apache.org/jira/browse/TAP5-1168
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core, tapestry-ioc
> Affects Versions: 5.3, 5.4, 5.2
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> Much like @Log, it would be nice to automatically integrate the OperationTracker into method calls.
> i.e.
> @Track("update login form")
> Object onActionFromLogin() { ... }
> I think @Track with a blank vlaue would identify the fully qualified method name. Otherwise, the value attribute would be used with String.format() and an array of the method parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira