[
https://issues.apache.org/jira/browse/TAPESTRY-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-1861:
-------------------------------------------
Fix Version/s: 5.1
> Frequently instantiated service implementations should have a specialized
> instantiation class created to prevent extra reflection calls
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1861
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1861
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-ioc
> Affects Versions: 5.0.6
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.1
>
>
> From the department of premature optimization:
> For services that are scope "perthread", the service implementation will be
> invoked repeatedly, via either invoking a constructor, or invoking a (static
> or instance) builder method on a module class.
> Currently each such instantiation requires calculating the method/constructor
> parameters (somewhat expensive) and invocations of the method/constructor via
> reflection (borderline expensive).
> The code responsible for this could track the number of instantitations and,
> on the second (or later) pass, create a "shim" class responsible for
> performing the same operations in a non-reflective way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
