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 2011/09/24 06:55:26 UTC
[jira] [Closed] (TAP5-1665) Tapestry could create non-singleton
services more efficiently
[ https://issues.apache.org/jira/browse/TAP5-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1665.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
Tapestry now generates a reusable "plan" for invoking constructors or service builder methods, and will retain that plan for scopes other than the default "singleton" scope. This skips a large amount of repeated analysis of fields and public methods and constructor/method arguments.
It does introduce a tiny change in semantics, in that an @Autobuild parameter to a service will be cached and reused, rather than recreated on each construction.
> Tapestry could create non-singleton services more efficiently
> -------------------------------------------------------------
>
> Key: TAP5-1665
> URL: https://issues.apache.org/jira/browse/TAP5-1665
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Affects Versions: 5.3, 5.2
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Labels: performance
> Fix For: 5.3
>
>
> For services that may be created again on each request, Tapestry does a lot of extra work to analyze the class, constructor and fields. It should be able to roll up all this information into a repeatable "plan" that can simply be re-executed on each subsequent instance creation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira