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 (JIRA)" <ji...@apache.org> on 2011/05/04 00:43:03 UTC

[jira] [Created] (TAP5-1519) Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker

Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker
----------------------------------------------------------------------------------------------------------------

                 Key: TAP5-1519
                 URL: https://issues.apache.org/jira/browse/TAP5-1519
             Project: Tapestry 5
          Issue Type: Improvement
          Components: tapestry-ioc
    Affects Versions: 5.2.5, 5.3.0
            Reporter: Howard M. Lewis Ship
            Priority: Minor


I've noticed that Tapestry is not always great about tracking what method or constructor is being invoked, which can make it harder to track down injection problems (which are automatically hard to start with).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (TAP5-1519) Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1519.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.0
         Assignee: Howard M. Lewis Ship

> Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1519
>                 URL: https://issues.apache.org/jira/browse/TAP5-1519
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3.0, 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> I've noticed that Tapestry is not always great about tracking what method or constructor is being invoked, which can make it harder to track down injection problems (which are automatically hard to start with).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (TAP5-1519) Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028508#comment-13028508 ] 

Hudson commented on TAP5-1519:
------------------------------

Integrated in tapestry-trunk-freestyle #336 (See [https://builds.apache.org/hudson/job/tapestry-trunk-freestyle/336/])
    TAP5-1519: Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker


> Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1519
>                 URL: https://issues.apache.org/jira/browse/TAP5-1519
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3.0, 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> I've noticed that Tapestry is not always great about tracking what method or constructor is being invoked, which can make it harder to track down injection problems (which are automatically hard to start with).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (TAP5-1519) Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028508#comment-13028508 ] 

Hudson commented on TAP5-1519:
------------------------------

Integrated in tapestry-trunk-freestyle #336 (See [https://builds.apache.org/hudson/job/tapestry-trunk-freestyle/336/])
    TAP5-1519: Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker


> Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1519
>                 URL: https://issues.apache.org/jira/browse/TAP5-1519
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3.0, 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> I've noticed that Tapestry is not always great about tracking what method or constructor is being invoked, which can make it harder to track down injection problems (which are automatically hard to start with).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (TAP5-1519) Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1519.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.0
         Assignee: Howard M. Lewis Ship

> Ensure that all calls to invoke methods and constructors with dependencies are tracked with the OperationTracker
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1519
>                 URL: https://issues.apache.org/jira/browse/TAP5-1519
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3.0, 5.2.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> I've noticed that Tapestry is not always great about tracking what method or constructor is being invoked, which can make it harder to track down injection problems (which are automatically hard to start with).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira