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 2010/05/15 00:36:42 UTC

[jira] Assigned: (TAP5-1000) When Autobuilding a class, the constructor to be used should be identified in the trace output

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

Howard M. Lewis Ship reassigned TAP5-1000:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> When Autobuilding a class, the constructor to be used should be identified in the trace output
> ----------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1000
>                 URL: https://issues.apache.org/jira/browse/TAP5-1000
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> The operation trace is useful for tracking down IoC injection problems, but in this case, it's slightly sketchy (I've elided some class names):
> * Autobuilding instance of ....SecurityFilter
> * Determining injection value of parameter #4 (....PageTitleExtractor)
> * Resolving object of type ....PageTitleExtractor using MasterObjectProvider
> I think there should be a line between #1 and #2 saying "Using constructor ...PageTitleExtract(....)  and listing the parameter types

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.