You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2013/01/07 22:06:13 UTC

[jira] [Updated] (TAP5-2046) Should use OperationTracker to track type of request (ajax component event, traditional component event, page render request)

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

Howard M. Lewis Ship updated TAP5-2046:
---------------------------------------

    Issue Type: Improvement  (was: Bug)
    
> Should use OperationTracker to track type of request (ajax component event, traditional component event, page render request)
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-2046
>                 URL: https://issues.apache.org/jira/browse/TAP5-2046
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>              Labels: feedback
>
> I often find myself doing a bit of work to identify, from the stack trace, what kind of request was received. It would be nice if Tapestry would use the OperationTracker to track the basics of a component request: ajax vs. traditional, component event type, containing page, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira