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/09/23 22:49:27 UTC

[jira] [Assigned] (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 reassigned TAP5-1665:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> 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
>
> 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