tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Created: (TAP5-1000) When Autobuilding a class, the constructor to be used should be identified in the trace output
Date Tue, 02 Feb 2010 18:22:18 GMT
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
            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.


Mime
View raw message