tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2046) Should use OperationTracker to track type of request (ajax component event, traditional component event, page render request)
Date Mon, 07 Jan 2013 21:36:12 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546286#comment-13546286
] 

Hudson commented on TAP5-2046:
------------------------------

Integrated in tapestry-trunk-freestyle #996 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/996/])
    TAP5-2046: Operation tracking improvement (Revision baabe981c2798f132d4d842a9ca5356e3d8d14ff)

     Result = ABORTED
hlship : 
Files : 
* tapestry-core/src/main/java/org/apache/tapestry5/internal/services/RequestOperationTracker.java
* tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java

                
> 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
>            Assignee: Howard M. Lewis Ship
>              Labels: feedback
>             Fix For: 5.4
>
>
> 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

Mime
View raw message